Radiobeacon Data Sharing by Forwarding Low Energy Transmissions to a Cloud Host

ABSTRACT

Remote actuation of machines or machine systems is realized by a system for coupling a radiobeacon to a smart device and in turn to a broader network. The smart device is configured as a proximity-actuated “community nodal device” by an application that operates as part of the system. The community nodal device is given instructions to function as a “soft switch”: to automatically “upswitch”, amplify, and broadcast low energy, local area radiobeacon “messages” to a cloud-based server, where the message is interpreted according to rules or policies established by an operator, and a command is transmitted for execution to a remote device. Conventional smart devices generally discard data not addressed to the owner of the smart device. Instead of discarding third party messages, the system preempts their handling, and using a soft switch formed from background resources, anonymously, without access to the message by a user interface of the proxy device, and without waiting for a network query from the host, engineers an “upswitched transmission” of radiobeacon-generated data to a cloud host. Advantageously, confidential sharing of ad hoc community resources results in a negligible load on background resources of the community nodal device. Messages may include a sensor data payload. Bit overloading enables a sensor data payload to be compressed into a few hundred bytes or less.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to and is a continuation of U.S. patent application Ser. No. 15/681806 filed 21 Aug. 2017, now U.S. Pat. No. ______, which is a continuation of U.S. patent application Ser. No. 14/967339 filed 13 Dec. 2015, now U.S. Pat. No. 9,773,310, which claims the benefit of priority under 35 U.S.C. § 119(e) from U.S. Provisional Patent Appl. No. 62/260313 filed 26 Nov. 2015 and from U.S. Provisional Patent Appl. No. 62/256955 filed 18 Nov. 2015 which are herein incorporated in full by reference for all purposes. This application is further related to U.S. Provisional Pat. Appl. No. 62/175141 filed 12 Jun. 2015 titled “Devices And Network Architecture For Improved Radiobeacon Mediated Data Context Sensing”, U.S. Provisional Pat. Appl. No. 62/136285 filed Mar. 20, 2015 titled “On-Board Battery Monitor and Radiobeacon Notification System”, and U.S. Non-Provisional patent application Ser. No. 14/301236 filed 10 Jun. 2014 titled “Tracking Device System”, all said patent documents being co-assigned and incorporated herein in entirety for all purposes by reference.

GOVERNMENT SUPPORT

Not Applicable.

TECHNICAL FIELD

This disclosure pertains generally to systems and methods for providing user services over an ad hoc crowd-sourced network. More particularly, the network comprises one or more radiobeacons each fitted with a low energy radio and one or more sensors, one or more proximate nodal devices configured to receive a message from said radiobeacons and relay that message to a cloud-based cloud host server, the cloud host server acting in turn to actuate one or more remote machines or machine systems according to user preferences.

BACKGROUND

The smartphone application known as “Uber” has brought into focus opportunities for sharing resources (such as vehicles) through a system designed to link available vehicles and drivers with guest users who have need of a ride. “Ride sharing” initially was a means for reducing rush hour congestion by small groups of co-workers who knew each other, but has evolved to operate essentially as a “for hire” service mediated through the Internet. However, the service has a high cost to the resource providers—the drivers—raising the issue as to whether sharing has become exploitation.

There is a need for resource sharing that operates with little or no cost to the resource provider, and in fact provides welcome reciprocity, such that roles may be interchanged and shared between resource providers and resource consumers. Sharing would be improved if providers and consumers both are able to draw on the resources of others to solve problems, and in turn provide resources that the system may use to solve problems such as living alone as we become more elderly, recovering a lost dog or cellphone, preventing mishaps to children who may otherwise not have adult supervision in this increasingly 7/24 workday world, and other challenges we face in everyday living.

More effort to explore the new sharing capacity of Internet-compatible nodal devices may help to ameliorate these and related problems. To date, efforts in this direction have necessitated that proprietary networks be built. No means for distributing shared resources fairly and without exploitation has been achieved. However, information sharing systems, whereby system resources are more efficiently shared in background, may yet achieve unexpected emergent properties, including synergies of function and new applications or properties.

SUMMARY

Disclosed are embodiments of a computer-implemented system operating to upswitch sensor data from a “low energy radio transmission” to a cloud host server in digital communication with a broad area network having a plurality of smart devices. Generally, the low energy radio transmissions are “radiobeacon signals”. By configuring smart devices to scan for qualified radiobeacon signal identifiers, ad hoc networks of widely used “smart phones” and other smart devices already in service may be created—these the networks surprisingly may be enabled to upload third party “radio messages” to a cloud host server, while causing little or no inconvenience to the owner of a private nodal device, who remains unaware of the background forward broadcast. A software application is provided that creates a “soft switch” in each user's device, effectively recruiting devices into a network of community nodal devices that facilitate sharing of computer resources, each device is configured to re-transmit other user's messages, regardless of message ownership, to a cloud host server, where the work of analyzing and acting on the message is initiated and completed. Any third-party message contents are not open to, or available in memory, for the owner of the private nodal device to see; and reciprocally, owners of nodal devices may rely on the nodal devices of other community members without loss of privacy, because the service is provided through background serves without using the memory resources of the proxy. This is particularly helpful because owners of radiobeacons benefit if they can receive messages even when their smart device is out of range of the low energy transmissions of their radiobeacons. By mutual reciprocity, those community members who contribute resources also benefit from the resources of others.

The system reconfigures commonly available “smart devices”, here termed more generally “nodal devices”; and recruits them for signal transmission using background services of the host device. An ad hoc network is created, made up of low energy radiobeacons and what are termed here “community nodal devices”, which refer to devices running an application of the invention. The application preempts the conventional logic to discard anonymous radio contacts and instead implements and enables sharing of background computing resources (hardware layers and stacks) of a device as needed to “upswitch” messages from a low energy radio band to an amplified signal compatible with internetwork transceivers, without notifying the private owner of a nodal device of the radio traffic in background on the device. In one sense, the message takes a “shortcut” through shared computing resources to a pre-determined cloud host address on an internetwork, and is then processed and ownership assigned according to the smart resources of an administrative server. Based on message contents and owner identification, owner instructions for actuation of remote devices are commanded and executed; community priorities may also be implemented, such as shared notifications to community members having a need to know about a hazard or a sensor output that has broader implications than just a private interest. Communities may be defined by a common membership, such as members of an institution, members of a neighborhood, members in a location or general area, or by user profile.

The system includes one or more radiobeacons having a sensor or sensor package, a clock, a processor with a memory for storing an instruction set, a radio emitter with antenna, such that the radio emitter operates at a first frequency and is configured to emit a broadcast signal in a low energy radio bandwidth. These radiobeacon signals include an identifier and a sensor data payload; the identifier and data are encoded in frames having defined bit structure. Radiobeacons are owned by an owner, who may also own a nodal device, and there may be many different owners who own one or more radiobeacons and/or nodal devices. By distributing and sharing a ‘software application’ that runs on any nodal device, owners form an ad hoc “community” of nodal devices capable of receiving messages from each other's radiobeacons, amplifying those signals, and upswitching them to an internetwork-compatible radioset for retransmission to a designated “cloud host” through a broad area network. The switching is made possible by a “soft switch” implemented by the application, the soft switch being assembled from communications and hardware “layers” or “stacks” built into the smart device. Thus the owner of a radiobeacon can receive a message even when a commonly owned (“co-owned”) smart device configured for receiving messages from the radiobeacon is out of range or out of service. Secondary message routing can be designated, for example, using shared community resources. Advantageously, content or context may be used to determine message routing and for establishing any actions to be taken in response.

Initially, a nodal device detects a low energy radio signal. Instead of discarding the message because the radiobeacon signal is not intended for the owner of the nodal device (i.e., the owner of the radiobeacon and the owner of the nodal device are distinct entities), the application is enabled to preempt the normal process and “upswitch” the message to the cloud host of the system (using background resources and at most a limited set of foreground resources). Once preempted, qualified messages are amplified and transmitted as a “forward broadcast” addressed (with an IP address and communicatively efficacious preamble and message structure, but maintaining the original message contents). The forward broadcast will include the unique identifier and sensor data payload of the original message, plus any timestamp or geostamp generated by the shared nodal device. This is accomplished without interrupting or alerting the owner of the nodal device to the background radio traffic, so that all messages remain private during uploading to the cloud host server. At the cloud host, the unique radiobeacon identifier (a 128-bit word as currently practiced) allows an administrative server to associate the message contents with its owner's account and to engineer a response.

The cloud host server then issues a command or notification to remote system assets based on the message contents. In this way a “shortcut” is constructed out of network components—using an owner's radiobeacon, a nodal device owned or under control of another member of the community, and cloud resources provided by the system—in order to effect a notification (such as a display on a screen or an alarm tone) or a machine transformation (such as raising a garage door). Owners may use this shared network to cause commands to be executed on remote machines, and in other instances the system may aggregate data or operate context-based or global policies that result in commands auto-generated by the system. Generally, a sensor datum or data included in the message triggers a particular response (as specific to the unique identifier); the response may be programmed by the user so as to be triggered by a particular sensor output, such as a button on a radiobeacon that is pressed, or a jolt that exceeds safe limits (as sensed by an accelerometer in a sensor package, as may be indicative of a fall or a collision). Responses may be as simple as a notification displayed on a user device, or more complicated, such as notification of a possible injury to a first responder, or forwarding a cardiac monitor signal to a physician's automated service, and so forth. In making a response, context provided by the sensor component(s) of the message is combined with other indicia and rules programmed into the system. Context may be as simple as time of day, or may involve more complex indicia such the expected arrival time of the next bus and the location of a friend. More generally, contextual information may be selected from database associations with an identifier, a timestamp, a proximity indication, a geostamp, from sensor data, or associations deduced from aggregations of messages received from a defined local area in a defined duration of time, or from trends detected in a pool of all messages, for example. The response may be pre-programmed by the owner of the radiobeacon (to whom the message is addressed, as identifiable from the unique identifiers associated with the message), or may be programmed to be triggered at a system level based on aggregate data received from many sources.

Any sensor data that can be digitized may be encoded in a message. In a preferred instance, the sensor data is “overloaded” into a standard message format. In another instance, additional frames or packets are included in the message. Sensor data may be simple or complex. Examples of sensors capable of digital output include photocells, radiation sensors, motion sensors, velocity sensors, accelerometers, jolt sensors, gyroscopic sensors, gesture sensors, gravitational sensors, magnetic sensors, compass sensors, clock sensors, switch open/closed sensors, vibration sensors, audio pattern detection sensors, vehicle performance sensors, biological agent sensors, biochemical agent sensors, chemical agent sensors, temperature sensors, humidity sensors, windspeed sensors, pressure sensors, location sensors, proximity sensors, global positioning satellite sensors, relative radio signal strength sensors, radio traffic sensors, and so forth. Sensors packages having audio sensors, such as a microphone or diaphragm, may include some level of acoustic pattern matching capability embedded in the sensor package; in other words, some preliminary filtering of the sensor output is used to minimize bandwidth. Various combinations of sensors may be provided in a sensor package.

The remote machine may be what is termed here an “effector machine”, indicating that the machine executes a physical transformation, such as a motor that opens a garage door, or what is termed here more generally an “actuation device”, indicating that the device may actuate a machine-generated display, or may recruit other machines and devices to perform designated functions.

Exemplary systems may include radiobeacons regularly broadcasting local conditions or canned messages such as merchant appeals. In some instances, radio emission is intermittent and periodic according to a schedule; in other instances, radio emission is triggered according to ambient conditions, such as crossing a threshold sensor output. In a preferred embodiment, a radiobeacon initiates a broadcast when a compatible nodal device enters radio proximity and the radiobeacon has new sensor output.

In one aspect, the invention includes methods for upswitching sensor data from a low energy radio transmission of a radiobeacon to a cloud host server in digital communication with a broad area network having a plurality of smart devices. Smart devices are well known and are generally privately owned. Each includes a processor, memory, and hardware layers for a) receiving low energy radio transmissions, b) installing and implementing software applications, c) operating software applications as a foreground service or as a background service, c) directing radio transmissions identifiably associated with the owner of a smart device to a foreground service, e) dumping radio transmissions not identifiably associated with the private owner of the smart device, f) marking radio transmissions with a timestamp when received, g) optionally marking radiobeacon transmissions with a proximity measurement or a geostamp where received, and h) amplifying, broadcasting, and receiving radio transmissions on a broad area radioset that is efficacious in communicating digitally with a cloud host server. The method includes steps for (a) providing one or more radiobeacons having a sensor or sensor package, a radio emitter with antenna, an encoder, a processor with supporting data processing circuitry, and memory for storing data and an instruction set to be executed by the processor, such that the radiobeacon or radiobeacons are configured for emitting a low energy radio transmission that includes a formatted unique identifier and a sensor payload, such that the formatted unique identifier and sensor payload define a qualified radio message, further such that each the radio message is associated with a private owner of the radiobeacon, the owner being identifiable by the identifier; and (b) installing an application on a smart device of the plurality of smart devices, such that the application is configured for preempting the smart device from discarding the qualified radio message when received by the smart device, instead the application operating to configure the processor, memory and hardware layers as a soft switch enabled to upswitchingly amplify and broadcast the radio message as a forward broadcast to the cloud host server, including in the broadcast the identifier and sensor payload, plus any preamble, network address of the cloud host server, any communication format as needed, and any timestamp, proximity measurement, or geostamp as generated by the smart device. In consequence, the smart device is transiently restructured by the software as a “community nodal device”, the community nodal device and soft switch being further characterized and defined as having the capacity for (i) automatically upswitching and forward broadcasting any qualified message in background to the cloud host server if the unique identifier is not recognized as being associated with the private owner of the smart device, without revealing the message contents to the owner of the smart device; and, (ii) automatically processing the message in foreground services if the unique identifier is recognized as being associated with the private owner of the smart device, revealing and acting on the message contents in foreground services to the owner.

The inventive methods also include receiving the forward broadcast at the cloud host, the cloud host having an administrative server configured with an instruction set and an administrative database, such that the instruction set including instructions for: i) parsing the forward broadcast so as to extract the unique identifier, the sensor payload, and any associated timestamp, proximity measurement, or geotag coded therein; and, ii) then, based on the owner identification, sensor payload, and any contextual information associated therewith, formulating a command or notification, such that the command or notification is based on rules associated with the owner identification in an administrative database and any rules implemented by a system administrator on behalf of a community of members; and finally, transmitting the command or notification over the broad area network to at least one smart device of the plurality of smart devices, to a remote machine, or to an actuation device.

As an added feature, the methods of the invention include provisions for “dumping” (i.e., discarding and erasing) any record or content of the message from the proxy device that aided in sending the message to the broad are network, and for releasing any computing resources shared by the community device in assembling the soft switch, unless and until another orphan message arrives.

As an added benefit, the system configuration implemented by the software, if the message owner's foreground services are unresponsive, automatically can suspend any process for processing the message in foreground services and automatically upswitch and forward broadcast the message in background to the cloud host server for disposition. The cloud host is able to parse the message, determine ownership by consulting a database, and based on rules associated with the private owner of the radiobeacon in an administrative database and any rules implemented by a system administrator on behalf of a community of members, take an action to the benefit of the owner and/or the community.

Command sequences take a number of forms. One method involves transmitting a command over the broad area network to at least one smart device of the plurality of smart devices, and generally this would be the response to a private message, essentially providing an alternative or secondary process for message delivery as preset by the owner.

Alternatively, in cases of general community interest, the method may involve transmitting the command to the plurality of smart devices, such that the command is a command to display a notification to a community of members having converted their smart devices to community nodal devices. This would be employed for example in matters of public safety, where a radiobeacon was reporting sensor data indicative of a fire, an auto accident, gunfire, or severe local weather.

More generally, the methods may also include provision for transmitting commands to a remote machine, an actuation device, or a plurality thereof, such that a physical transformation will be achieved, for example opening a garage door, or rolling down a car window, where the owner is not in physical proximity and needs assistance in performing the action. The command to the plurality of remote machines or actuation devices may be a command to execute a machine action or to actuate a device.

The nature of the action (or notification) may depend on the contents of the sensor payload. Sensor or sensor packages on radiobeacons will vary, but may be selected from a photocell, a radiation sensor, a motion sensor, a velocity sensor, an accelerometer, a jolt sensor, a gyroscopic sensor, a gesture sensor, a gravitational sensor, a magnetic field sensor, a compass, a local time sensor, a switch open/switch closed sensor, a vibration sensor, an audio pattern detection sensor, a vehicle performance sensor, a biological agent sensor, a biochemical agent sensor, a chemical agent sensor, a temperature sensor, a pressure sensor, a humidity sensor, a windspeed sensor, a location sensor, a global positioning satellite sensor, a proximity sensor, a relative radio signal strength sensor, or a radio traffic sensor, and so forth.

Location information leads to special applications. In some instances, location is known because the radiobeacon is stationary in a fixed location known to the administrative server. In other instances, radiotagged objects (having a radiobeacon attached) are portable, but their location can be deduced from recent radio contacts with other beacons or signals having known locations. An aggregation of radio messages from a plurality of community members may also be useful in establishing location, and some smart devices are equipped with GPS sensors, allowing precise position centering.

Thus the action taken can be targeted to a particular location. Other sensor context can also be important in directing action. Context as a whole, as known to the administrative server from historical and aggregated data stored in an administrative database, can be queried to determine the parameters of action to be taken. Aggregates of messages, all indicating tight traffic in a local area, could be used for example, to invite community members to find routes around the area. Similarly, community members could be offered direct routes to an event based on routes and experiences of others headed to the event.

In yet another application, the method may involve compiling and sharing a map or plot display in which sensor data is graphically displayed in aggregate, or graphically displayed with trend lines, or graphically displayed with an updatable tracking function. This can be of use, for example, in tracking lost objects. In at least one application the method may include providing a cloud-based service for graphically displayed the location of a lost object as tracked by its radiotag in the form of a track or path superimposed on the map, such that the map is updated when the administrative server receives a fresh radio contact and location of the lost object, the track including a chronological record of recent contacts in a mapped sequence.

Also provided here are devices, software, networks and system architectures for radiobeacon sensor payload sharing by the methods of the invention. These and other elements, features, steps, and advantages of the invention will be more readily understood upon consideration of the following detailed description of the invention, taken in conjunction with the accompanying drawings, in which presently preferred embodiments of the invention are illustrated by way of example.

It is to be expressly understood, however, that the drawings and examples are for illustration and description only and are not intended as a definition of the limits of the invention. The various elements, features, steps, and combinations thereof that characterize aspects of the invention are pointed out with particularity in the claims annexed to and forming part of this disclosure. The invention does not necessarily reside in any one of these aspects taken alone, but rather in the invention taken as a whole.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the present invention are more readily understood by considering the drawings, in which:

FIG. 1 is a schematic view of an exemplary application of a system of the invention for campus security.

FIG. 2 is a schematic view of an exemplary network and system of a second embodiment of the invention.

FIG. 3 is a schematic view of an exemplary network and system of a third embodiment of the invention.

FIG. 4 is a schematic view of an exemplary network and system of a fourth embodiment of the invention.

FIGS. 5A and 5B (two sheets) illustrate a block diagram of a general method of deploying and using an exemplary system of the invention.

FIG. 6 is a bit diagram figuratively showing the structure of a message.

FIG. 7A is a block diagram of functional components of a radiobeacon having limited computing resources in radio communication with a compatible nodal device, the nodal device having a processor and application for receiving a radio signal loaded with sensor data and switching that signal to a broad area network.

FIG. 7B is a block diagram of functional components of a second radiobeacon in bidirectional communication with a nodal device, the radiobeacon and the nodal device both having a processing capacity and a non-volatile memory capacity for storing instruction sets.

FIG. 8 is a schematic view of system for upswitching sensor data from a low energy radio transmission to a cloud host server in digital communication with a broad area network having a plurality of smart devices.

FIGS. 9A, 9B and 9C are plan and perspective views of an exemplary radiobeacon configured for use in the inventive systems and networks.

FIGS. 10A and 10B are exploded views of an exemplary radiobeacon configured for use in the inventive systems and networks

FIG. 11 is an animation showing a radiobeacon transiting a defined area so as to come into proximity with a series of three nodal devices.

FIG. 12 is a schematic view of a system and network having three radiobeacons, a plurality of community nodal devices in proximity to one or more radiobeacons (one of which is depicted as a smartphone), a cloud host server, and an exemplary data structure and notification process in the cloud host server. One radiobeacon is tagged to an object in motion.

FIG. 13 is an exemplary view of a system and network having three or more radiobeacons, a nodal device hub, an optional computing device, a cloud-based cloud host server, and three client devices.

FIGS. 14 and 15 are views of an alternate radiobeacon and beaconmate of the invention. Shown is a simplified command and control system utilizing a beaconmate, a nodal device, and a cloud host server.

FIG. 16 is an exemplary view of a radiobeacon with beaconmate in digital communication with a nodal device. Transmission of commands can be direct (dashed arrow) or indirect (solid arrows).

FIG. 17 is a component level view of a beaconmate in indirect radio communication with a smartphone through a community nodal device.

FIG. 18 is a simplified view of a system for using a beaconmate to operate a smart device according to the systems and methods of the invention.

FIG. 19 illustrates a view of a message in which “bit overloading” of frames is used to transmit sensor signals within the bit structure of a standard communications protocol.

FIGS. 20A and 20B are screenshot views of graphical user interface displays. The displays are generated by an exemplary software application of the invention on a nodal device or other computing machine.

The drawing figures are not necessarily to scale. Certain features or components herein may be shown in somewhat schematic form and some details of conventional elements may not be shown in the interest of clarity, explanation, and conciseness. The drawing figures are hereby made part of the specification, written description and teachings disclosed herein.

Glossary

Certain terms are used throughout the following description to refer to particular features, steps or components, and are used as terms of description and not of limitation. As one skilled in the art will appreciate, different persons may refer to the same feature, step or component by different names. Components, steps or features that differ in name but not in structure, function or action are considered equivalent and not distinguishable, and may be substituted herein without departure from the invention. The following definitions supplement those set forth elsewhere in this specification. Certain meanings are defined here as intended by the inventors, i.e., they are intrinsic meanings. Other words and phrases used herein take their meaning as consistent with usage as would be apparent to one skilled in the relevant arts. In case of conflict, the present specification, including definitions, will control.

Radiobeacon—refers to a device having a low power radio emitter for broadcasting a local intermittent message, the message containing a unique identifier (conventionally termed a UUID) indicative of a device manufacturer, model and “serial number” to be associated with an owner, optionally one or two frames or “values” (conventionally termed “major” and “minor” values) containing location or sub-type information, and preferably at least one sensor output in digital form, wherein the sensor output may be transmitted in a dedicated frame in the message, or may be overloaded into the major or minor values, or even in the UUID. Certain smart devices may emulate radiobeacons by programming a low energy radioset in the device to emit radiobeacon messages in a proper format. This includes bluetoothed devices generally, iBeacons, any smart device such as a cellphone, laptop or personal assistant device having a beacon functionality, and enhanced devices in the internet-of-things. Radiobeacons can be installed so as to be generally stationary even if portable or can be mobile, as when hand carried or affixed to an object or device that is intended to move or is moving. Radiobeacons may be integrated into networks, generally as radio emitters with no or limited radio reception, and have limited range. In some instances, radiobeacons may have limited capability as transceivers, and may receive radio signals and communications, such as for receiving remote program updates, or may include a radio receiver capable of detecting radio traffic in close proximity to the radiobeacon.

In the figures, radiobeacons intended to be generally stationary are indicated by a “star”; and radiobeacons that are intended to be portable or in motion are indicated by a “circular disk”, however these indicia are selected for purpose of illustration and are not intended to be representative of or limiting with respect to structure.

“Broad area networks” (BANs) are defined broadly to include wide area networks (WANs), local area networks (LANs), virtual private networks (VPNs), and metropolitan area networks (MANs), including wireless radio networks, cellular networks, and any patchwork of local area networks, wired or wireless, operating with a broadband, geographically extended range and Internet connectivity at some point or points. These networks have varying hybrid structures, but are generally long-distance communications networks that cover cities, states, countries, and may be global. The Internet is the largest broad area network that has been implemented and includes a variety of backbone connections and branch connections. “Internetwork” is used here sensu lato to indicate any BAN that includes at least one digital connection to Internet-based “cloud” services, where the connection(s) to the Internet may be wired, wireless, or a serial or parallel composite of wired and wireless segments making up a digital connection. Digital connections include bidirectional and unidirectional segments.

“Nodal device”—refers to any electronic device with a processor, non-volatile memory for storing program instructions, and supporting circuitry and hardware for executing commands from a user, for wireless communication with a broad area network portal or interface (i.e., communicating with an internetwork) and for wireless communication from and/or to a radiobeacon or other low energy radio device, where the two radio interfaces (a BAN interface and a low energy radiobeacon interface, sometimes termed a BLE interface) are operated on separate radiosets at different frequencies and power levels. Nodal devices typically have a plurality of connections, whether permanent or intermittent, bidirectional or unidirectional, to a plurality of broad area networks, including cellular, wide area, and local area wireless networks, and to low power radiobeacon emitters when at close range. Each device is defined as a node. Nodal devices include modern smartphones, personal digital assistants, laptops, notebook computers, tablet computers, desktop computers, or any equivalent device that can store and hold programs and data, execute programs, receive and/or transmit information and commands via wired or wireless channels of communication over a plurality of networks. Nodal devices also include radio-equipped computing machines in the form of a “hub” or “base station”. Many such devices may also be programmed to function as mobile radiobeacons for emitting low energy radio messages, and may be provided with sensor units or packages, such as GPS sensor and location calculating packages, or accelerometry, gyroscope, compass and motion sensor packages. Radiobeacon emissions are distinct and independent of the radio pings used to identify cell towers.

Nodal devices typically have inherent functionality for: i) running applications on foreground resources or background resources, ii) receiving low energy radiobeacon transmissions, iii) discarding radiobeacon transmissions not identifiably associated with the nodal device's owner, iv) directing radiobeacon transmissions identifiable to an owner of a nodal device to a foreground service (such as a user interface for answering telephone calls or displaying text messages), v) marking radio transmissions with a timestamp when received, vi) optionally marking radio transmissions with a proximity measurement or a geostamp (sometimes termed a “geotag”) where received, and vii) transmitting and receiving radio transmissions on a broad area radioset that is communicatively compatible with an internetwork portal.

Nodal devices include “foreground services” and “background services” having different command tree priorities. Commands for operations that should be performed to completion without being interrupted are “foreground commands” and utilize foreground resources (such as a user interface). Commands for operations that can be interrupted by a foreground command and continued at a later time are “background commands” and utilized background resources. In this way, foreground commands typically have a predetermined completion time, whereas background commands may have an extended completion time, depending on the level of interruption by foreground commands. Embodiments of the invention take advantage of the fact that the device controller will typically not consume the full parallel bandwidth, so background resources are typically executed on background resources without noticeable delay. As defined here, “foreground services unit” refers to a structural association of hardware layers, stacks, and elements, including associated software or firmware, needed to perform foreground commands or routines; “background services unit” refers to a structural association of hardware layers, stacks, and elements, including associated software or firmware, needed to perform background commands or routines. For example, a foreground services unit may include a dedicated memory for storing data such as call logs and voicemail and a hardware interface for accessing user services, whereas a background services unit may include transitory cache memory and other hardware assigned when needed to perform a background task, and may not include a direct user interface.

“Upswitchingly transmitted” refers to a process that is generally implemented by software configured to organize hardware layers and stacks into a “soft switch” for detecting and receiving a message from a radiobeacon on a first radioset, and switching the message to a second radioset for amplified transmission to a broad area network, typically an internetwork. Also involved in the switching is formatting the message with a network preamble communicatively compatible with the broad area network and adding any timestamp or geostamp generated by the nodal device. In some instances the “soft switch” may be implemented with firmware but is generally conducted using hardware layers, stacks, and background resources under control of a software application installed on and implemented on the nodal device. Radio messages that are normally discarded, those having no identifiable association with to the owner of the nodal device are instead switched and “forward broadcast” to a broad area radioset for re-transmission at higher power and are then discarded without sharing the contents with the owner of the nodal device, and without the knowledge of or active participation of the owner. Nodal devices having the software application, or otherwise being configured to perform the here described ‘soft switching’, are termed “community nodal devices”.

“Community nodal devices” are distinguished by the functionalities of a software application as installed and implemented in the device; the application organizes background services into a “soft switch” to upswitch messages received from community-associated radiobeacons, forwarding the messages to an internetworked cloud host server while operating in background on the device, and more particularly while not accessing foreground services for decoding, displaying, aggregating, or storing the message contents of the radiobeacon. Community nodal devices are also configured to receive notifications from an internetworked cloud host server and in some instances may be programmed to execute functions in response to a command from the cloud host server. The software application and the cloud host server operate together in systems and methods of the invention.

“Timestamp” is an automated function performed as a background service in most nodal devices. Each radio contact detected is assigned a record having a time and date.

“Geostamp” is an optional function performed as a background service in some nodal devices. Each radio contact is assigned a record having a datum indicative of proximity to a known location, or a GPS coordinate. Radio signal strength at a particular frequency is generally indicative of proximity. Cloud host servers may further refine location using aggregated data. But geostamping is a nodal device function, much as a camera associates an image in memory with a location determined by accessing GPS signals and making a calculation of latitude and longitude, generally on a dedicated chip included in the device for that purpose.

“Registering”—refers to a programmed node action of storing a record of a radio contact, a timestamp, optionally a geostamp, and/or at least one sensor datum in a memory module of a radiobeacon. Records in storage are generally retrievable, such as by accessing or searching a table or a database, for example, or other data retrieval systems known in the art. Records may also be uploaded to a higher layer in a network, such as to a server or other cloud-based service.

“Network”—refers to a whole world network (“internetwork”), a local area network (LAN), a wide area network (WLAN), or a wired network (and combinations thereof) having one or more nodes through which signals are received and processed or retransmitted. A conventional network may be wired or wireless, for example a Zigbee radio network or a BLUETOOTH® low energy radio network of devices that are linked by a handshake protocol. Networks are differentiated as to whether their wireless emissions are low power and short range (i.e., “bluetoothed” and MANET networks) versus higher power and longer range as would be understood by one skilled in the art. Also included are telephone networks linked to wireless networks, such as AIN (Advance Intelligent Network), MSTO (Mobile Switching Telephone Office, and PSTN (Public Switched Telephone Network).

Mesh network—relates to a network having nodes capable of generating signals as well as relaying signals of others according to a peer-to-peer network. In a partial mesh network, some nodes are connected to just one or two other nodes. Many mesh networks operate across multiple radio bands. As known in the art, Firetide and Wave Relay mesh networks have the option to communicate node-to-node on 5.2 GHz or 5.8 GHz, but communicate node to client on 2.4 GHz (802.11). These frequencies are both designated for low energy radio bands and thus are intended for local area and micro area networking, typically with a common owner.

Mobile ad hoc network—relates to a continuously self-configuring wireless population of mobile devices functioning as internetwork routers for signal traffic; for example a MANET network, as known in the art, functions on top of standard internetwork linking protocols established for the Internet and includes addressing capability to forward traffic from one mobile device to another through a wireless network according to rules governing traffic and parsimonious utilization of nodes, where the owner of the network owns a controlling interest in all network resources and teaches methods to exclude others from using network resources.

“Owner”—is a user having ultimate control of a device that is part of a network. Control of an exemplary device in a network may be exclusively assigned to a single owner, or may be delegated or shared without loss of ownership according to permissions granted by the owner. An owner-user is any entity having delegated or shared authority to control a device in part or in full, without determination of ultimate control. Control is generally determined by an owner in a first person sense, as based on assignment of permissions as known in the art. Third person owners are affirmatively termed “anonymous users” or “operators” or “community members” sensu lato, without limitation and are non-controlling of network operations conducted in background on their community nodal devices.

“Sensor”—includes any device having a measurement function, either qualitative or quantitative, parametric or non-parametric. Generally this includes, by example, sensors for temperature, motion, velocity, acceleration, jolt, pressure, humidity, windspeed, lightness, radiation, switch open/switch closed, and so forth. Also contemplated are sensors for vibration, magnetic field, gravity, gases such as methane, CO, CO₂, CBD vehicle performance indicia, QR sensors, aerosol particulate levels, history of sub-zero temperature, history of product over-temperature, analytes such as chemical or biological substances, and the like. More generally some sensors can detect biological agents, biochemical agents, and/or chemical agents for example. Sensors also include radio devices designed to detect radio traffic, such as a “ping” from a proximate radio device. Such sensors may detect relative signal strength; other sensors may be GPS sensors having a function of reporting a location or location specification data, and may combine data such as by registering a radio contact, a time stamp and a location. Sensors may function as triggers when linked to an enabled device having instructions for receiving and acting on a sensor output, where the machine is linked to the sensor through a network having at least one node and at least one cloud host server.

“Hive”—may refer to a group of radiobeacons owned or controlled by a common entity, such as an individual, a family, a private business, a public institution, or any group having definable membership.

“Remote machine”—may be what is termed here an “effector machine”, indicating that the machine executes a physical transformation, such as a garage door opener, or what is termed here an “actuation device” more generally, indicating that the device may be a display for displaying content to a user, or may be enabled to recruit other machines and devices to actuate performance of designated functions.

“Contextual content”—(also termed here, “environmental input”, “contextual data” or “stimulus input”) refers to any bit or message of data corresponding to a sensor output received by a processor for transmission, and may include data related to temperature, light intensity, smoke, voltage, sound, motion, displacement, acceleration, humidity, pressure, radiation, button-press event, compass direction, or to report daylight levels, traffic levels, history of sub-zero temperature, history of product over-temperature, noise levels, NOX levels, aerosol particulate levels, and unusual noises such as gunshots or sirens, or self-reporting, such as reporting a low battery level, or other stimulus or sensor data, without limitation to these example contextual contents. In some instances a sensor is a switch having two positions such that the datum is an indication that the switch has been tripped, such as a button switch when pressed, a photocell that has been triggered by light, or a motion sensor that has been tripped by motion, and so forth. More sophisticated sensors may also be used, such as radiation detectors, chemical detectors, biological detectors, and sound discriminators, where the output may be relatively simple to represent digitally, but the sensor module itself is a complex analytical device. Sensors associated with radiobeacons may be used in clusters, such as to report sets of data for temperature, humidity, windspeed and barometric pressure, or to report a clustermap of urban micro-local conditions such as traffic levels, noise levels, NOX levels, and particulate levels, with map-pins showing unusual noises such as gunshots or sirens. Self-reporting, such as reporting a low battery level, is also included in the scope of contextual data. Preferred sensors are miniaturized so that they may be co-housed with the radio controller and emitter module. Generally the sensor module will include a controller for conditioning and digitizing the output and may include a microcontroller function for execution of basic program steps, where the instruction set is stored on-board in non-volatile memory or as firmware, or is executed when received by a radio receiver associated therewith. Contextual data may also be used to enable security features of the radiobeacon communications systems.

Contextual information for making rule-based decisions may be selected from database associations with an identifier or identifiers, any timestamp data, any proximity data, any geostamp data, any sensor data, or from associations deduced from aggregations of messages received from a defined local area in a defined duration of time, or from trends detected in a pool of all messages.

A “server” refers to a software engine or a computing machine on which that software engine runs, and provides a service or services to a client software program running on the same computer or on other computers distributed over a network. A client software program typically provides a user interface and performs some or all of the processing on data or files received from the server, but the server typically maintains the data and files and processes the data requests. A “client-server model” divides processing between clients and servers, and refers to an architecture of the system that can be co-localized on a single computing machine or can be distributed throughout a network or a cloud.

“Computer” means a virtual or physical computing machine that accepts information in digital or similar form and manipulates it for a specific result based on a sequence of instructions. “Computing machine” is used in a broad sense, and may include logic circuitry having a processor, programmable memory or firmware, random access memory, and generally one or more ports to I/O devices such as a graphical user interface, a pointer, a keypad, a sensor, imaging circuitry, a radio or wired communications link, and so forth. One or more processors may be integrated into the display, sensor and communications modules of an apparatus of the invention, and may communicate with other microprocessors or with a network via wireless or wired connections known to those skilled in the art. Processors are generally supported by static (programmable) and dynamic memory, a timing clock or clocks, and digital input and outputs as well as one or more communications protocols. Computers are frequently formed into networks, and networks of computers may be referred to here by the term “computing machine”. In one instance, informal internet networks known in the art as “cloud computing” may be functionally equivalent computing machines, for example.

“Processor” refers to a digital device that accepts information in digital form and manipulates it for a specific result based on a sequence of programmed instructions. Processors are used as parts of digital circuits generally including a clock, random access memory and non-volatile memory (containing programming instructions), and may interface with other digital devices or with analog devices through I/O ports, for example.

General connection terms including, but not limited to “connected”, “attached,” “conjoined,” “secured,” and “affixed” are not meant to be limiting, such that structures so “associated” may have more than one way of being associated. “Fluidly connected” indicates a connection for conveying a fluid therethrough. “Digitally connected” indicates a connection in which digital data may be conveyed therethrough. “Electrically connected” indicates a connection in which units of electrical charge are conveyed therethrough.

Relative terms should be construed as such. For example, the term “front” is meant to be relative to the term “back,” the term “upper” is meant to be relative to the term “lower,” the term “vertical” is meant to be relative to the term “horizontal,” the term “top” is meant to be relative to the term “bottom,” and the term “inside” is meant to be relative to the term “outside,” and so forth. Unless specifically stated otherwise, the terms “first,” “second,” “third,” and “fourth” are meant solely for purposes of designation and not for order or for limitation. Reference to “one embodiment,” “an embodiment,” or an “aspect,” means that a particular feature, structure, step, combination or characteristic described in connection with the embodiment or aspect is included in at least one realization of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment and may apply to multiple embodiments. Furthermore, particular features, structures, or characteristics of the invention may be combined in any suitable manner in one or more embodiments.

“Adapted to” includes and encompasses the meanings of “capable of” and additionally, “designed to”, as applies to those uses intended by the patent. In contrast, a claim drafted with the limitation “capable of” also encompasses unintended uses and misuses of a functional element beyond those uses indicated in the disclosure, referencing Aspex Eyewear v Marchon Eyewear 672 F3d 1335, 1349 (Fed Circ 2012). “Configured to”, as used here, is taken to indicate is able to, is designed to, and is intended to function in support of the inventive structures, and is thus more stringent than “enabled to” or “capable of”.

It should be noted that the terms “may,” “can,'” and “might” are used to indicate alternatives and optional features and only should be construed as a limitation if specifically included in the claims.

The various components, features, steps, or embodiments thereof are all “preferred” whether or not specifically so indicated. Claims not including a specific limitation should not be construed to include that limitation. For example, the term “a” or “an” as used in the claims does not exclude a plurality.

“Conventional” refers to a term or method designating that which is known and commonly understood in the technology to which this invention relates.

Unless the context requires otherwise, throughout the specification and claims that follow, the term “comprise” and variations thereof, such as, “comprises” and “comprising” are to be construed in an open, inclusive sense—as in “including, but not limited to.”

The appended claims are not to be interpreted as including means-plus-function limitations, unless a given claim explicitly evokes the means-plus-function clause of 35 USC § 112 para (f) by using the phrase “means for” followed by a verb in gerund form.

A “method” as disclosed herein refers to one or more steps or actions for achieving the described end. Unless a specific order of steps or actions is required for proper operation of the embodiment, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the present invention.

DETAILED DESCRIPTION

Radiobeacon data sharing for triggering remote machine action is realized using proximity-actuated soft switches and system network architecture. Messages from radiobeacons containing sensor data output are upswitchedly transmitted to a cloud host server of an internetwork (uniformly referenced in the drawings as cloud host 1000). Nodal devices are configured to function as soft switches by an installed “application” typically run as software. The soft switch function allows the nodal device to upswitch signals received from a low energy radiobeacon to a “whole world” or “broad area” network in amplified form and in a communicatively compatible format for reception by a cloud host server. In the cloud host server, a response is initiated according to rules and policies established by the owner of the radiobeacon and/or by the administrator of the system. The response may be a command to action or a notification transmitted to a remote machine.

The cloud host server receives radiobeacon output from compatible “nodal devices” in proximity to the radiobeacon. Put another way, the radiobeacon recruits compatible nodal devices based on proximity, not by ownership, where proximity is defined by radio signal strength emitted by the radiobeacon. With low energy radiosets, as currently practiced, proximity for effective radio transmission has a limit of about 150 feet, and location can be defined by relative signal strength. Proximity may be further refined by GPS location of the nodal device relative to the radiobeacon (i.e., a geostamp supplied by the nodal device), or by a calculation that involves aggregating data received by the cloud host server and assigning contacts a location based on history of proximity to one or more radiobeacons having known locations. Radiobeacons having fixed or otherwise known locations are generally indicated here in the drawings by a “star”; mobile radiobeacons may be indicated by a round body or may be incorporated in any of the smart devices depicted, many of which emulate beacon function or can be converted into a radiobeacon by installing a software application of the invention.

Broadcasts are termed “messages” because they preferredly include a “data payload” having output from a sensor or sensor package associated with the radiobeacon. On receipt, a compatible nodal device will register the message and add a timestamp (and a geostamp when available). Conventionally this information is then discarded if the nodal device determines that no policy or rule associates the message with the owner of the device; however, by installing an application of the invention in a nodal device, the nodal device acquires capability to access a cloud host of the invention, and message policies will include instructions for processing and rebroadcasting third-party messages in background (but where the message contents remain anonymous, occult, and encoded so that the owner of the “proxy” device is not notified or permitted access to the message contents without special permissions). At the end of the upswitching process, no record of the contents of the message can be retrieved from the proxy nodal device and encryption may be used as known in the art to ensure privacy, whereby only the cloud host server will decrypt the message. The broadcast forward, however, includes the original data payload of the message, a timestamp as received, and a network address for the cloud host, so that it can be routed to the cloud host server. Based on ownership of the radiobeacon as determined from the original message contents, and on sensor data in the message, along with any contextual information that is relevant, the cloud host server accesses a database or instruction sets, determines a user preference or an administrative preference for some appropriate action in response, and initiates the pre-configured action, for instance, instructing a remote machine or machine system to execute an action that the owner has requested according to the time, place, context, and/or any condition reported in the sensor data.

In other instances, the cloud host server will take collectively beneficial action, such as by sharing a map showing aggregated data indicating updated traffic conditions, or alerting users according to their profile of any events of interest. The actions can range from calling an emergency operator in the event that the radiobeacon detects and reports data consistent with a vehicle accident or injury, or actuating a camera, or lowering a window in an overheated vehicle, or unlocking a car without using a key, helping a user find their lost keychain with their cellphone, helping find their lost cellphone (using the radiobeacon in the cellphone) with their keychain, or displaying a map having an overlayer of aggregated local microarea weather data collected from multiple radiobeacon sensors by intermittent transmissions from nodal devices. Other examples are demonstrated below.

Unlike common commercial radiobeacons designed to emit canned notifications according to user or merchant input, the preferred radiobeacons include at least one sensor unit and an encoder for transmitting sensor output in a formatted message that is understood by the cloud host server. Data structures for transmitting sensor data in low energy radio signals will be described in detail below.

The transmissions from community-shared nodal devices may be promiscuous, and generally occur in background services on the nodal device, utilizing only a small fraction of the nodal device capability, and thus the application operates in background essentially as a network switch for particular radio contacts, recruiting hardware as needed to amplify, relay and route the message from a local low energy radio emitter, through a broad area radioset of the device, and a defined IP address of a cloud host server. The nodal device has two radiosets, and uses lower link layers to add a timestamp (and optionally a geostamp) when switching the data from a low energy radio receiver to an amplifier/transceiver, and formats the message according to accepted communications protocols for each radioset, but does not otherwise process the data for display or storage. In short, the application does not provide for foreground display or access to the message. Thus data transmission is opportunistic but also discreet.

In some instances, a radio emission by a nodal device, such as a cellphone station ping, will actuate emission of sensor data from a radiobeacon sensor package in response. In other instances, the radiobeacon will intermittently emit a message according to current conditions or according to a regular schedule, and any compatible nodal device that receives the signal will execute the broadcast forward capability installed as part of the application. The application for recognizing the message, switching the data, and assigning resources to amplify, route, and rebroadcast the message runs in background and is generally installed on the nodal device from a distribution server or by other download services. In this way, users having nodal devices may share resources needed to switch lower level radiobeacon transmissions onto a network through which a shared cloud host server can receive the transmission. All users benefit by services provided by the cloud host server. These include accessing locations of lost objects (objects, or pets, to which a radiobeacon may be attached), monitoring ambient conditions, receiving notifications of adverse conditions, aggregate sharing of local events, remote notification of home alarms, and reduced insurance risk, for example.

Also, the application may be installed with a feature to convert the nodal device into a radiobeacon and to harness the network clock in the hardware. A message may then be broadcast to a cloud host server in background with a network timestamp and a sensor data payload as configured by the user, such as accelerometry, motion sensing, and location data, each datum with a timestamp, and may be accessed by owners seeking a lost cellphone or mobile device, for example, on which the application is installed. Community smart devices fitted with the corresponding software, upon encountering a local broadcast of any device, will report the radio contact to the cloud host server, if the radiobeacon has been tagged as lost the server will flag the contact for special processing, and will correlate contact information from multiple hits so as to issue a report or periodic notifications tracking the lost device.

Owners of radiobeacons may also access their own smart device, where “smart device” is taken broadly as any device capable of functioning under control of a software “application” of the invention. In response to a signal from a radiobeacon, amplified and upswitched to a broad area radioset by the smart device—where the owner of the radiobeacon has configured the server to execute a command to a remote machine, such as a camera, a cellphone, a garage door, or a panic alarm, for example, or even the smart device itself—a physical act results. Thus a smart device such as an iOS or Android-enabled cellphone becomes a platform for operating and controlling one or more remote machines according to rules established by an owner of the radiobeacon and implemented through the cloud host.

FIG. 1 is a schematic view of an exemplary application of a system 10 of the invention for campus security. An example of the system in use is presented as an introductory demonstration. While described generally as a series of steps, the underlying system and network structure, devices and components are also described in the figures that follow.

In this example, an owner 11 of a pocket radiobeacon 12 actuates a switch, causing the switch output to go “high”. This is essentially a sensor having two values, HIGH and LOW. When HIGH, the radiobeacon is triggered to emit a message having the device UUID and a data payload including the sensor value “HIGH”. The device has limited computing power, but advantageously readily transmits simple messages with just the press of a button. Thus it is well suited as a “panic button” in this example, where HIGH triggers a system response. Advantageously, the owner of the radiobeacon does not need a cellphone in hand to access the system. The radiobeacon is lightweight and convenient and can be pocketed on a keychain for example or pinned to a jacket.

Here owner 11 encounters a hazard or is in danger, and in a first step 1, actuates a pocket radiobeacon 12 to summon help. Because the radiobeacon has limited radio range, the message cannot be directly ported to a broad area internetwork. However, in step 2, a community nodal device 14 in the possession of a passing stranger 13, is able to detect the radio transmission and upswitch the message to a cloud host server 1000 as shown in steps 3 and 4. The community nodal device 14 is programmed with a software application of the invention; the application functions in background to a) amplify the transmission, b) attach a router-compatible forwarding address, and c) broadcast forward the message, routing information, including a timestamp, and optionally including a geostamp.

Using the UUID, the cloud host server 1000 identifies owner 11 in an administrative database. Using contextual information, such as proximity to radiobeacons having locations known to the system, or location information generated by community nodal device 14, the cloud host server makes a rules-based decision 5 to cause a first responder to be dispatched to the scene 6, and/or to issue a general notification 7 to all members of a community 8. Lighting in or around the owner's position may also be increased 9 or strobed to signify that help is on the way and surveillance cameras can be switched to live feed. These functions can be automated through the cloud host server or semi-automated to include interactive displays and a human operator. Other alarms may also be actuated.

Generally, community nodal device 14 is a “smart device” having application instructions for operating a soft switch for switching messages between two radiosets of the nodal device, the radiosets operating on radio networks or “bands” that are otherwise not connected. Generally one is a low energy radioset for generating, sending and receiving a radiobeacon signal having a UUID and one or more optional frames. The other radioset in the nodal device is a broad area radio transceiver that transmits an amplified broadcast forward to an internetwork transceiver or portal. The executable instructions for the soft switch are installed by loading the inventive application onto the nodal device, as from a distribution server or other downloading service such as a near field communications port, and are generally memory resident in the smart device. Notifications are sent to individual personal smart devices 8 a operated by members of the community (if the devices have been configured with the software application), and thus a benefit is provided to all community members. The reciprocal responsibility is that those same smart devices become community resources for upswitchingly transmitting radiobeacon messages belonging to others to the cloud host server. Because the sharing functions occur in background, little expense and no effort is incurred by the community as individuals, and again because the messages are handled in background, no display or storage of the messages is permitted. Owners of beacons can use the system with a reasonable expectation of privacy such that the operator of the system establishes policies in which certain information (including owner identification and sensor data payload) will not be shared unless contextually relevant or is presented as de-identified aggregate data. Alternatively, notifications may be sent to a select list of “friends” identified by the owner of the beacon, and for whom the appropriate permissions have been implemented on the cloud host server.

FIG. 2 is a schematic view of an exemplary network and system 20 of a second embodiment of the invention. A system is shown having a radiobeacon 21 with edge-mounted touch button 21 a and a nodal device (here a community nodal device 14) in a first location 23, a cloud host server 1000, and in a remote location 24, an actuation device 25 (here a friend's smartphone), a remote machine 2000, and a second actuable device 3000. Bold arrows indicate radio contacts; a dashed line indicates an optional configuration. Software for coordinating the system and network architecture is installed in the radiobeacon 21, the nodal device 14, the cloud host server, in actuation devices 25 and in machines or actuable devices (2000, 3000) as needed. Generally actuation devices 25 function as clients of cloud host 1000 when executing commands. The system thus has three functional blocks, a radiobeacon-nodal device pair (23, dashed box), a cloud host 1000, and downstream actuation cluster (24, dashed box) having one or more actuation devices 25 and associated effector machines. Actuation of machine functions may involve generating a display, closing a switch, powering down a machine, triggering an output, and so forth. Actuation may be controlled directly from the cloud host, or may involve an intermediate downstream controller as represented here by smartphone 25). The radiobeacon 21 and the controller 25 may belong to an owner and a friend, for example, whereas community nodal device 14 may belong to a third party member of the community, acting anonymously in background. In other circumstances, device 25 may play the role of community nodal device in transmitting messages from yet another radiobeacon (not shown) to the cloud host, the yet another radiobeacon belonging to yet another third party, and so forth. Thus network and computing resources are shared equitably based on a principle of “mutual reciprocity”.

By limiting exchange of data between background and foreground resources of a nodal device, messages can be upswitched for redirection onto the higher power radioset of the nodal device without compromising the privacy of the owner of the radiobeacon from which the message originates. Messages are encoded in the radiobeacon and may be further encrypted by methods known in the art for some applications.

Embodiments of the radiobeacons of the invention are configurable by an individual user to help solve various problems, such as finding lost objects, monitoring pets or the activities of small children, hospital patients, and so forth. The radiobeacon is a comprehensive solution to locate and track missing pets, people, luggage, inventory, tools and items of interest tagged with a radiobeacon, and may also be used to alert users when there is a sensor output change, such as a very sudden jolt. In preferred embodiments the radiobeacon incorporates various sensors and control mechanisms that make the radiobeacon a versatile multi-function device which can remotely control other devices such as smartphones, tablets, or computers through the network 20, indirectly through a community nodal device 14 as shown here, or directly as disclosed in earlier filed U.S. Pat. Doc. No. 14/301236, filed 10 Jun. 2014, titled “Tracking Device System”. The exemplary system 20 illustrated here is instrumental in shaping and creating a market for the “internet of things” by allowing a user or network of users to seamlessly share sensor data and control remote devices, also offering the capacity to provide a regional, local, or global “picture” of environmental conditions such as temperature, traffic, and trends in a particular area, or simply a collaborative picture of all tagged dogs and cats active in a particular city neighborhood, venue or locale at a specific time, for example. The device functions with a single-button>multifunction interface (SBMFI) (e.g., single button 21 a—operates to control command response based on rules linked to button press patterns, long, short, duplexed and operated with Boolean statements about other variables, such as time of day, day length, user profile, and weather forecast, for example, and go on from there). The tree can also be built with more trunks, each a button press on a keypad. In a keypad, more complex patterns can be encrypted, levels may be established, favorites may be encoded, all with only a rudimentary feedback pattern of confirmation, an LED as a mouseover (with the finger), a capacitive screen, a zoom gesture, and the like. Of course, browser screens could be the greatest return but the radiobeacon itself is intended as a lean selection of essential components for the needed power to performance ratio, so a minimalist approach is favored. Another approach is to add a companion and/or co-computing locus that includes a more expansive user interface (see FIGS. 14-18), and achieve a level of complex simplicity in operation of low energy network clusters and communities. Both approaches offer substantial advantages to the user, as does the SBMFI approach.

FIG. 3 is a schematic view of an exemplary network and system of a third embodiment 30 of the invention. In this view, community nodal devices 31 and 32 relay messages from local area 33 (in which generally stationary radiobeacons indicated by stars 34, 35, 36 are positioned), to cloud host server 1000. Depending on the message, an actuation device 25 at a remote location 38 may be used to actuate machines 2000 and 3000. Alternatively, remote machine 2000 may be capable of directly receiving commands from the cloud host server (dashed arrow). The system uses background resources to carry radio traffic without using foreground resources of community nodal devices (31, 32) during radio encounters with any proximate radiobeacons (34,35,36). Because the messages are all short and condensed data structures that can be interpreted at lower machine levels, no inconvenience to user's results, and “system load” rebalancing is minimal. In network embodiment 30, nodal devices forward broadcast signals from multiple radiobeacon devices, as shown here, each message (parallel arrows) being separated from the next and being discarded after processing and transmission to the cloud host 1000.

FIG. 4 is a schematic view of an exemplary network and system of a fourth embodiment 40 of the invention. In this embodiment, stationary radiobeacon (41,42,43) traffic is relayed through an ad hoc network of nodal devices (44,45) in the local area 46. The radio messages are parsed by a cloud server 1000, and commands or notifications are transmitted to multiple remote recipients. In each instance, the command can result in machine actuation (2000,3000) or in a display 47 at remote locations 48 a, 48 b, 48 c, respectively. Actuation device 25 functions as a remote controller for machine 2000. The cloud host directly controls machine 3000. Thus the system and network architecture uses a combination of radiobeacons and smart devices to manage tasks for multiple owners and community members.

In this instance, messages from radiobeacons can be relayed in a series of hops from a first nodal device 44 to a second nodal device 45, but at some point are picked up by a broad area internetwork portal and routed to cloud host server 1000. A plurality of radiobeacons, a plurality of nodal devices, a plurality of cloud servers, and a plurality of machine effectors or actuation devices may be involved in any active system cluster 40.

FIGS. 5A and 5B (two paired sheets) show a block diagram of a more general method of deploying and using an exemplary system of the invention. Represented in a first box (dashed outline) are rudimentary functional blocks (50 a,50 b,50 c) corresponding to sensor measurement, initialization, and broadcast from radiobeacon 50. In step 50 a, a sensor output is generated. Typically the sensor is an on-board sensor unit or a sensor package. These steps may be repeated at any interval dictated by the needs of the user and by context, or may be initiated cybernetically in response to a trigger such as a change in a sensor value above a threshold. Current generations of radiobeacons may broadcast messages at ten millisecond intervals, thirty second intervals, or any convenient time—as when in proximity to a nodal device, for example, and operate as limited resource computing devices capable of simple repetitive actions.

“To measure” (i.e., “measuring”) is an operation 50 a having the quality of digitizing a contextual condition or event and can be as simple as a step for determining whether a button is pressed and held or not, or an operation such as collecting and digitizing a photocell output, which may include steps for amplifying and filtering as needed, or more complex operations such as providing a memory component and instructions for determining a measurement change over an interval of time.

The measurement data is then incorporated into a message through an initialization operation 50 b in which a preamble and any message formatting is performed. The broadcast is then sent 50 c via a low energy radio module, and the process is iterated as needed or directed. Compatible devices in radio proximity may receive and decode the measurement data in the radio broadcast 50 d.

The sensor unit or package is in electrical contact with circuits for basic processor functions and program execution. A simple processor may function as an “encoder” for initializing a message, in which a digital radio signal is “loaded” with the sensor data while conforming to an underlying radio communications protocol format (as disclosed earlier in U.S. Prov. Pat. No. 62/175141 filed 12 Jun. 2015 titled “Devices and Network Architecture for Improved Radiobeacon Mediated Data Context Sensing”, which is co-assigned and co-pending). A radio emission by a radiobeacon that carries a sensor data payload is termed a “message”.

Next in the figure, nodal device (51, dashed outline) is represented as a series of functional blocks, including steps for transmitting a “broadcast forward” 53 containing the message to a cloud-based administrative server or cloud host 1000 (continuing in FIG. 5B). The nodal device includes a transceiver for scanning 51 a and receiving low energy radio signals. The scan function is represented as an iterative loop 51 b. When a qualifying radiobeacon message is detected (YES), the signal is timestamped 51 c and optionally geostamped 51 d.

If owner identification information associated with the radiobeacon message is associated with the owner of the nodal device (51 e, YES), the message is conveyed to foreground services for immediate action or processing. The message is processed, stored in memory 51 g, and any action appropriate for the message is taken. The process of scanning 51 a and capturing 51 b radio transmissions repeats.

If not (51 e, NO), software of the invention preempts normal operation of a nodal device, which is to discard unrecognized signals. Instead of discarding the message, the message is preempted and processed in background services 51 h. Background services are an ad hoc organization of hardware resources needed to shunt or “upswitch” the message to a broad area network radio transmitter for broadcast forward. Preemption is triggered when the radio signal is identified by a software application of the invention as a message from a qualified radiobeacon but the ownership of the message is not recognized by the nodal device.

Beginning at 51 h, those messages not meeting the common owner test 51 e are handled anonymously in background services. The message is switched 51 i to a communications layer or stack in the device, initialized 51 j for broadband transmission to an internetwork-compatible receiver, and forward broadcast at 51 k. The message is then discarded and the process ends 51 m by clearing background resources. This process, including structuring of a “soft switch” at 51 i, is directed by a software application supplied to users of the inventive system. Soft switch 51 i switches the message from a low energy radioset in the nodal device to a broad area radioset in the nodal device, the latter operating with protocol communicatively compatible with an internetwork portal and network architecture. End function 51 m is generally conducted by existing machine functionality in the nodal device. Nodal devices are constructed to discard (i.e., “dump”) unrecognized low energy radio signals and to record and store owner-recognized radio signals in memory for processing. A variety of permissions and policies control the “dump” function. The software applications of the invention are executed so as to preempt and re-route signals recognized by the application as “messages” to soft switch 51 i. The soft switch has been created to broadcast forward those messages to a designated cloud host server. Although the nodal device 51 discards and clears the message from local resources at 51 m, the forward broadcast 53 is transmitted at 51 k to network 1000 for processing.

Furthermore, if foreground services are not responsive (51 f, NO), then the message may be processed in background services in the same way as an anonymous message. The nodal device can be programmed so that owner will receive a push notification, including a command to open a screen on the user interface, depending on priority and context associated with the owner's identification or preset instructions as known to the cloud host. Essentially the owner gets a second opportunity to receive and see the message from a co-owned radiobeacon. Alternatively, even if the owner is unresponsive, the cloud host may be preconfigured to aggregate the message contents, such as any sensor payload, for later retrieval. The cloud host has access to other messages, and may also aggregate message 53 with messages from other community members, forming a larger picture that the owner of the radiobeacon can later access.

Forward broadcast 53 is captured by an internetwork portal and routed as per standard IP protocols to a designated cloud host 1000 operated by the system administrator. Each incoming message is parsed for content, including owner identifiers, sensor content, including any location information derived from the radiobeacon (many are in fixed locations) or from a geostamp applied by the nodal device. Location may be further deduced by the server from a pattern of contacts of nodal device 51 with proximate radiobeacons or nodal devices having geostamping capability that emulate radiobeacons.

Cloud host server (dashed box, 55) is a fully resourced computing environment for establishing rules-based policies and permissions. The server includes user accounts and at least one database 54 for storing owner information, parsing incoming messages, and processing or aggregating data. Aggregated data is used in making context-based decisions on behalf of individual users or on behalf of user communities according to rules established by the community and the system administrator.

The cloud host server may be accessed with a graphical user interface or through an application program interface, and includes an administrative interface for maintenance, subscription management, and quality assurance. Typically the server is accessible through a dedicated web site, and may be able to publish and transmit web pages to individual users or communities of users in response to a query or command. Relational databases may include user profiles and aggregated data and may be dis-identified to protect identities of individuals where release of that level of detail is inappropriate. The system may also include a distribution server for installing the software application, which will typically include instructions for upswitching community messages and instructions for pushing notifications and for accessing the administrative server for account setup and maintenance.

The broadcast forward 53 is first parsed 55 a for owner identifiers, sensor data in the original message payload, and any timestamp or geostamp in the broadcast. If the originating radiobeacon is owned by a co-owner of a nodal device (55 b, YES), a command response or notification 56 may be initiated directly to the owner through either a wireless IP mode or a landline. If the sensor data is such as to actuate a trigger 55 c for a defined action, the command response 56 will be given accordingly, either as a command or a notification. If any context, including the realtime merger of events and conditions that envelop the message, dictates 55 d a modified decision, the response 56 will reflect the context to the extent permitted by policies established by the owner of the beacon and any global policies or prohibitions exercised by the administrator of the system. Messages may be re-routed as appropriate. While not shown, more than one internetwork server may be recruited for making a response. Thus the cloud host has the capacity, for example, to perform searches and to incorporate search data before issuing a command or notification 56.

Communications with client devices and machines are frequently bidirectional. Responses may be logged and stored 55 e along with the initial commands and notifications for later retrieval, for use in tracking lost items, and for other aggregative uses. Several examples of applied uses are provided at the close of this section. The cloud host server will generally complete a process of responding to an incoming message and then stop 55 f until another message arrives, but may be programmed to refresh its command executions at desired intervals, or when conditions change, or on selected calendar dates, for example. Thus the location of a friend can be reported on the occasion of a birthday, for example. The uses increase exponentially as the internet of things (TOT) expands.

In a final step, illustrated in dashed box 57, the cloud host server 55 transmits or otherwise conveys an actuation instruction 56 to a machine effector and/or actuation device (indicated collectively in exemplary variants). The instruction 56 may be conveyed to an “effector machine” or an “actuation device”. These are generally smart machines having a limited but sufficient level of signal recognition and computing capability to perform a transformation in a physical sense, such as opening a garage door, turning off a stove, steering a driverless vehicle to a preselected destination, updating a display to show a map, or initiating a telephone call to an emergency responder when a strong jolt is detected by an accelerometer and gyroscope sensor package, and so forth. In some instances the cloud host administrator will reserve action, or will aggregate data over time or geographical area before initiating an action. These and other features allow the operator of the system flexibility to initiate actions according to a broad range of contextual information and to learn by observing historical, geographical, and diurnal patterns, for example.

Effectors and actuators 57 include remote machines 3000, that may be operated directly as described already, or indirectly through a controller 4000, and may also include smart actuation devices 25 generally, whether addressed to individuals or to communities of users, and may also include other types of actuator devices 2000, where the object is to take an action and end 57 b until further instructions are received. Chains of active machines having a sequence of actuation may also be engineered using the systems and network architectures of the invention.

FIG. 6 is a bit diagram showing the digital structure of a first message 60 a and a second message 60 b streamed in series, the two parts making up a full radio message 60. The second message includes a sensor payload 64, repeats major and minor values (62,63), but does not repeat earlier broadcast identifier 61. In this example, a radiobeacon is configured to emit an extended message that includes its UUID (61, generally a unique 128-bit word registering the make, model, and serial number of the radiobeacon device, as is sufficient to assign ownership), any major and minor values (62, 63), as can be indicative of location, sub-location, including owner secondary identifiers, generally in a highly structured format. The bracketed frames are representative of digitized data as formatted in a bluetoothed message. Sensor payload 64 may be transmitted in a second message 60 b, shown here as a sensor value having sixteen bits in a frame in this example. Added sensor data may be streamed by appending concatenated message parts formatted as shown. The bits are numbered for illustration, but any number of bits in a frame are contemplated, including bits from 4 to 8 to 16 to 32 to 64 without limitation thereto. The bitstrings of each frame may be organized as bytes, but are more typically termed “values”. Additional frames may be used, as indicated by an ellipsis at the lower right, to stream additional data. Added serial messages may be streamed each for example with realtime sensor data or with data from other components of the sensor package housed in the beacon. Alternatively, sensor data may be “stuffed” into the primary frames of the first message as illustrated and discussed with reference to FIG. 19.

Communications must follow a format standard. Bluetoothed format is one such coding language. In some variants, the host device or base station is configured to transmit relevant configuration information to the radiobeacon in order to tell that radiobeacon specifically what configuration of command language is needed. This can be implicit (e.g., the nodal device receives the preamble and UUID values received from the radiobeacon and enters a database or other source of information to determine a proper command protocol for the various subsystems of that particular radiobeacon, or explicit (e.g., where the radiobeacon explicitly instructs the nodal device what protocol to use, or even provides a communication properly formatted and with an appropriate preamble so that the receiving device is prompted to run a particular application in order to invoke the desired message handling operations. For example, radio emitters may be designed to emit radio signals according to a bluetoothed low energy interface standard and/or an iBeaconed communication protocol standard as known in the art, and may also be configured to emit radio signals according to data structures of the inventive network architectures and software applications.

FIG. 7A is a block diagram of functional components of a “limited-computing-resource” radiobeacon (dashed box, 70) and a compatible nodal device (dashed box, 71) in one-way radio communication where indicated by arrow 72. Typical nodal devices are provided with a processor 71 a and an “application” (*, indicating resident processor-compatible instructions in memory 71 b) for receiving radio signal 72 and for upswitching it to a transceiver 71 c having power and frequency configured for broad area radio transmission to a cloud host 1000, also termed here a “broadcast forward”.

Radio emitter module 70 a of the radiobeacon loads sensor data from sensor unit 70 b into a radio signal and emits message 72 on antenna 70 c. The loading function may be performed by a software encoder programmed within the emitter module, which functions as a microcontroller with on-board non-volatile and volatile memory (not shown). The message is configured to contain an identifier value (UUID) and a payload of digital sensor data. Optionally one or more of the sensor data values may be insertedly encoded in the standard frames of a bluetoothed low energy radio protocol by overloading a frame as is described later with reference to FIG. 19. The encoder function may be integrated into the radio emitter module and is implemented using software or firmware or a combination of both. Radiobeacons may be battery powered or otherwise powered as known in the art.

Typically these radiobeacons will operate at about 2.4 GHz or/and about 5 GHz, depending on the jurisdiction. For most purposes, only the 2.4 GHz band is used, and the two bands will be considered to be “one band” dedicated to bluetoothed protocols unless otherwise distinguished. With respect to nodal devices, multiple bands may be available for communicating to a broad area network through any compatible telecommunications system, including cellphone networks, and wired networks, or combinations thereof. These multipotent networking devices will be considered to be operating with one broad area frequency or band, merely for conceptual simplicity, the details of which may vary with regulatory jurisdiction.

In the networks of the invention, a soft switch configured in a nodal device by a software application of the invention provides the needed machine configuration to upswitch radio signals from a bluetoothed low energy radioset to a broad area radioset. The software is configured to facilitate sharing of radiobeacon signals with nodal devices that in turn may “upswitchingly transmit” data received from the radiobeacon to a broader network (optionally including multiple nodal devices), and thus serves as a mobile access point for forward broadcasting of messages to the Internet at large. In special circumstances, radio signals may be “downswitched” from a broad area radioset to a bluetoothed low energy radioset equipped with a receiver.

Nodal device 71, shown here schematically, switches signal 72 to a longer range transceiver 71 c and network for delivery to cloud host 1000. The nodal device may include the following functional blocks: transceiver(s) 71 c; processor 71 a, memory 71 b, foreground services 71 d (often a mix of software and firmware); a user interface 71 e; and background services 71 f. Background services typically involve commands and function calls to lower machine and link level stacks or routines built into the machine hardware, typically lacking any direct user interface capacity. The device also includes two antennae: 71 g and 71 h. Antenna 71 g receives signals 72 from low energy radiobeacon 70. Antenna 71 g may also emit beacon-like signals advertising its own proximity. Antenna 71 h is a higher power, broad area antenna configured for sending and receiving signals to a cloud host, and may use wireless systems or a cell tower network at radio frequency bands as jurisdictionally established. Additional antennas may be used as required and in some instances may be successfully combined in a single antenna package.

The switch is typically a “soft switch” and is implemented by software (*) executed by the processor of the nodal device using background resources. However, firmware may be used to supplant or supplement software in devices having integrated circuits capable of automating the required instruction set in a solid state pattern of logic gates and memory circuits. An ASIC is particularly favored for larger volume deployments of community nodal devices, but software is favored for installing into existing network and devices or when periodic across-network updates are anticipated.

At the cloud host 1000, generally the sensor data is extracted from the message using software developed to administer user needs. Relational databases may also be used to store data and detect changes or trends in the data. Based on ownership privileges, rules-based instructions, and context, the cloud host server will transmit a signal to a remote machine 2000 or other actuation device as warranted.

Nodal device 71 may be a stationary “hub” or a mobile device such as a smartphone and may be equipped with a portal to the Internet, an internetwork, a wide area network, or a local area network with Internet option, either wired or wireless; in this instance a wireless transceiver with antenna 71 h is shown. Hubs are described in U.S. patent application Ser. No. 14/301236, said patent application being co-assigned and co-pending. Processor 71 a is configured to read and execute an application (*) or applications from non-volatile memory 71 b and to receive and process the radio signal 72 as received on antenna 71 g and amplified by transceiver 71 c. Depending on the contents of the radio signal, particularly with respect to any contextual data encoded in the signal or known to the system, the processor will issue an instruction. For example, if co-ownership is recognized by the system, the foreground services unit 71 d will push an alert or a notification onto the user interface 71 e. This is often the case for hub installations in a private home or office. The device may also include a policy controller that controls foreground functions according to permissions set by the user.

The sensor unit or package 70 b may include one or more sensors. Sensor output to be encoded in a frame or frames for transmission may include temperature, light intensity, smoke, voltage, sound, motion, displacement, acceleration, humidity, pressure, radiation, button-press event, compass direction, daylight levels, traffic levels, noise levels, NOX levels, ODB reports, and unusual noises such as gunshots or sirens, or self-reporting, such as reporting a low battery level, or other stimulus or sensor data, without limitation thereto. In some embodiments, sensor data may also include a combined multi-axis motion sensor and temperature sensor integrated into a BTLE radio emission module 70 a, which includes an accelerometer, a gyroscope, and a magnetometer for each axis. Sensor power is commonly derived from the host, but in selected applications, a separate power supply may be provided.

FIG. 7B depicts a more complex system with a radiobeacon (top, 80) and the nodal device (bottom, 71) described in FIG. 7A. In this instance, however, both the radiobeacon and the nodal device have capacity to execute program instructions and have bidirectional radio capability represented by radio signal 73 (double headed arrow). The radiobeacon is configured with added processing capacity 80 a, including a dedicated signal encoder 80 b, non-volatile memory capacity 80 c for storing an instruction set, and an independent power supply. The radiobeacon is also provided with a sensor unit or package 80 d. The radio module 80 e of the radiobeacon is for example a bluetoothed low energy radio transceiver and is adapted to convert radiobeacon identifier and sensor data from sensor unit 80 d to a transmission “message” using encoder 80 b. Signals may be transiently stored in volatile memory as needed. One or more receive and/or transmit amplifiers may optionally be used to amplify signals received or sent, as known in the art, but the transceiver is typically a low energy transceiver as used here to advantage for qualifying radio contacts limited to a discreet local area.

Both the radiobeacon and the nodal device include a radio transceiver (80 e, 71 c) capable of receiving and transmitting low energy radio signals, but the nodal device includes a second radioset 71 c for transmitting and receiving at higher power over a wireless wide area network. While each device includes compatible antenna (80 c, 71 g) for low power inter-communication; the nodal device will also include a longer range antenna 71 h for sending and receiving signals to and from a cloud host server 1000 on a broad area internetwork.

The cloud host 1000 may then transmit or otherwise convey an instruction to a compatible remote device, shown here as an actuation device 25, a smartphone under control of user 85 for example, having capability to transform something in a physical sense, such by displaying a location of a lost cat or lost keys on a map of the neighborhood, or sounding an alarm, or displaying a reminder message from the cloud host server every Friday.

The exemplary radiobeacon 80 of FIG. 7B further comprises supporting circuitry that is adapted to perform programmed instructions from memory or as supplied in firmware. Memory 80 c also includes one or more storage devices capable of storing bits of RAM data. Thus these radiobeacons 80 provide a richer computing resource environment when compared to the more limited resource radiobeacons 70 illustrated in FIG. 7A. The sensor module may include one or more sensors as describe earlier, and may be capable of doing periodic data dumps in conjunction with memory, plotting trends, or detecting threshold levels. Generally however, these advanced functions are contained in the cloud host server, where the computing resources are larger.

Nodal device 71 may be a stationary “hub” or a mobile device such as a smartphone and may be equipped with a portal to the Internet or a network, either wired or wireless; in this instance a broad area wireless transceiver with antenna 71 h is shown. Hubs are described in U.S. patent application Ser. No. 14/301236, said patent application being co-assigned and co-pending.

Memory 71 b in the nodal device 71 is typically larger than that of a radiobeacon. Memory includes any combination of volatile memory and non-volatile memory (for example, DRAM, SRAM, flash memory, SIM, EAROM, EPROM, EEPROM, and/or myriad types of other memory modules).

The nodal device is provided with a clock (not shown) so that radio contacts (including cellphone tower contacts) can be timestamped for storage. Optionally, incoming data such as photographs may also be geostamped if the device is provided with a global locator. The processor 71 a capability may include a subroutine for transmitting GPS coordinates from a GPS receiver to a cloud host over a cellular or other wireless interface. For forward broadcasting, any location data may be associated with the sensor data payload in radiobeacon message 73. The processor is further adapted to execute one or more programs which, upon detecting a specific control signal, modify the functionality of the radiobeacon (or vice versa) according to the type of signal detected, or alternatively, by the contents of the signal provided (e.g., sensor data and identifiers embedded within the radiobeacon message, as described elsewhere herein). In one embodiment, once the nodal device functionality has been changed according to a governing policy or multiple policies, actions such as push notifications (generated by foreground services unit 71 d) may be performed without a direct request from the owner of the host device. The foreground services module has access to a user interface 71 e and may be configured, using applications and systems of the invention, to display or announce alerts in response to triggers, threshold levels, or signatures contained in the sensor payload received from the radiobeacon, either directly or indirectly (as via a server in receipt of the radiobeacon sensor payload and having programming capacity to craft notifications directed to particular users based on that sensor data, including input stimuli generally, and other data in one or more relational databases, for example).

Radiobeacon messages not addressed to the owner of the nodal device (i.e., addressed to a third party) are handled by background services unit 71 f. These features generally require some degree of programming that may be executed by the host processor after the needed software application (*) is installed in the nodal device by accessing a distribution server or other program distribution methods known in the art. Alternatively, the instruction set may be accessed through computing resources in the cloud, although this is less resource parsimonious.

In some instances, the nodal device 71, the radiobeacon 80, and an actuation device 25 are owned by a common owner 85. According to permissions by the common owner, nodal device 71 will shunt services to foreground services 71 d if possible, and that failing, will forward broadcast the message to device 25. In the case of nodal devices 14 controlled by third party users, as shown for example in FIG. 1, will switch messages to broad area radio transceiver 71 c and antenna 71 h for broadcast to cloud host 1000 as a background service implemented by the software application (*) in memory.

Generally as part of nodal device processor functions, a “policy controller” comprises logic adapted to control signals received from connected devices and is implemented as one or more software routines resident in one or more memory sources and executed by the processor. In other devices, the policy controller may take the form of a network controller. The policy controller comprises logic adapted to store information pertaining to designated policies. For example, a given policy may require muted ringers and reduced lighting when a wireless device is determined to be in a certain zone, as triggered by a sensor data input from a radiobeacon. Some policies are implemented in the foreground services module 71 d; others in the background services module 71 f or in lower logic sub-routines and levels of machine function.

Also, in many embodiments, a policy controller facilitates the transfer of one or more control signals or commands to a network of devices. In one variant, the message signal comprises a command disposed within the message frames as formatted in 802.11 WiFi Interface protocol. In other variants, the radiobeacon message may comprise a plurality of vendor-specific information or data elements which may be used to convey policy information to a smart device. It will be recognized, however, that other software-enabled approaches for communicating with community nodal devices may be used as is consistent with the invention, including for example use of bluetoothed communications signals, or cellular forward/reverse traffic or control channels, etc. as applicable. These capabilities are commonly encountered in “smart devices”, including those used here as nodal devices for information switching from one network to another.

FIG. 8 is a schematic view, showing an exemplary computer-implemented system 900 for servicing an owner in need of conveying a command or notification to a remote machine or actuation device in response to a sensor data payload from one or more radiobeacons. This description supplements but does not limit the remaining figures and specification. This exemplary system demonstrates a radiobeacon 34, a community nodal device 14, a cloud host 1000, and an owner's personal device 911, optionally being operated at a distance to actuate a remote machine 2000. Surprisingly, the system operates without any involvement of an individual owner 85 and can perform simultaneous operations on behalf of the owner and other community members, engineering sharing of the needed computing and sensor resources from multiple devices.

Implicitly, the coordinated implementation of a system of the invention requires that appropriate instructions be provided, thus the invention also includes software components stored in memory and accessible to a processor as needed. Beyond that, the network and the owner's smart device all function without intervention by, or exposure to, an operator; i.e., the system can function essentially autonomously. The final recipient or owner 85 of the radio message is essentially entirely relieved of the operation of the system (except during setup and when instructions are input on a personal smart device, 911). As embodied here, the system requires no direct human involvement in making the low energy radiobeacon transmissions, in upswitching a message using a community nodal device 14 as a proxy, or in processing the amplified message, context, identifier, and sensor payload by the cloud host, administrative server, and administrative database. Thus any command to an effector machine or actuation device 3000 is entirely automated and is handled by smart logic implemented in the system at several levels.

Beginning at the top of FIG. 8, a stationary beacon 34 broadcasts 902 a radio message with sensor payload. A community nodal device 14 captures 904 the qualifying message and begins processing by comparing the identifier in the message with identifiers associated with the owner of the nodal device (i.e., its owner). These nodal devices are frequently smart phones and rely on identifiers to distinguish traffic addressed to their owners from anonymous transmissions that are frequently encountered in the sea of radio transmissions around them. Incoming radio traffic is typically discarded 899 by conventional devices if the owner of the message is not recognized.

The invention changes that, preempting qualified radio messages for forward broadcast in background. Qualified radio signals are no longer discarded (X). By installing and operating an application of the invention (or a firmware equivalent thereof), radio messages received from anonymous devices are instead identified by characteristic messages identifiers as belonging to a broader class of community members. The nodal device is restructured by the application to organize nodal device hardware, stacks and layers into a “background services unit” having capability to detect, receive, amplify, and upswitchingly transmit radio messages to said cloud host according to rules implemented by the application. The restructured device includes a “soft switch” for shunting the messages to a broad area radioset for forward broadcast.

A decision tree 905 is shown. First, “YES”, if the owner of the radiobeacon 34 is associated with the owner of the nodal device 14, then the radio message is processed 906 by the foreground services unit of the nodal device. If the owner's response is confirmed (907, as can be merely an unlocked screen or a ringtone in foreground services, any response that engages a graphical user interface or an automated foreground process), then the message is logged and stored 909 according to protocols established by the owner. Because foreground services are involved, the owner 85 may directly participate. Workflows 908 through 911 are bidirectional in that the user may directly control the process. Typically an action is taken 910 and the process ends. The user need not be directly involved but can later access the transaction. The message, timestamp, and any action taken is recorded in memory on the device 14.

On the other hand, (“NO”, 905) if the identifier in the radio message is not associated with the owner of device 14, then the message is processed by the “soft switch” of the invention and (instead of being dumped 899) is upswitched 920 as follows: Hardware connections are restructured to direct the message to a broad area radioset, restructuring or “encoding” it to conform to an internetwork compatible communications protocol (such as by adding a preamble and a routing address), while retaining the original message content. The radioset amplifies the message and forward broadcasts it on a dedicated antenna 922 so that it may be picked up by an internetwork portal and relayed to a designated cloud host 1000 from essentially anywhere around the world. The application is also configured to attach any timestamp, proximity measurement, or geostamp generated by the nodal device to the radio message before the radio message is amplified and upswitchingly transmitting to the cloud host.

Because the message is not presented to foreground services, it remains anonymous, and is neither displayed nor stored on the community nodal device 14. Although the incoming message may be augmented with a timestamp and even a geostamp from the receiving nodal device, the message is not stored and is not retrievable on a user interface—so as to preserve privacy and prevent accumulation of clutter. After all, the design of the inventive system is such that de minimus resources are borrowed or shared in background to achieve a community service, hence any unneeded function that would be an added burden on the owner's device is avoided—e.g., clearly, using any permanent memory resources would not be needed. While RAM memory is often needed for background stack execution, the memory is either wiped or written over after the upswitch and the broadcast transaction 924 is completed.

The upswitched message is transmitted through cloud host 1000 to a remote machine 911. In the cloud, under control of an administrative server 924, the message is logged, parsed to retrieve the message contents, and any context, identifiers, including UUID and major and minor values, plus any sensor data payload, including concatenated streaming sensor payloads structured as described in FIG. 6, are processed. Rules-based associations are made, typically using a relational database or other intelligent processing capability.

Associations may be limited to owner-associated context and rules, or may be expanded to include rules for parsing data in the context of aggregated data such as location, time of day, or issues of community interest such as microarea weather events, vehicle accidents, community events, disturbances, including earthquakes, fires, and so forth. Thus both personal notifications and commands and community-directed notifications and commands may be generated by the server. Example of community-directed notifications include summoning of first responder assistance or increasing light levels on a street at night in a particular block; an example of a personal command includes a command to map directions to the location of radiobeacon 34. In this respect, associations based on proximity and chronicity with respect to location and time are likely to serve as context for any actions implemented by the system host.

In this exemplary system, if the owner's response is not confirmed, a command or notification is broadcast or otherwise transmitted 926 to a personal device 911 operated by the owner of the message. This may take the form of a notification or may result in execution of a series of instructions. The owner's device may also actuate a peripheral 3000, and may cause execution of commands, causing direct actions such as to turn down a volume control, respond to an email, lock a vehicle, open a garage door and so forth, before ending 928. Direct contact 912 with the owner 85 is not a precondition for taking action, although the owner may set up a policy controller to monitor any commands and receive sensor data in the form of a graphical or audible display on a user interface. Summaries may be announced using voice synthesizer technology known in the art.

For those messages belonging to the owner of device 14, if foreground services 906 are non-responsive or not available, such as being “out of service”, or if the owner's confirmation 907 is insufficient according to rules established in the administrative server, this invokes an alternate or secondary pathway. Message processing is preempted 930 by the application running in device 14. Again as a background process, relying on background services and hardware layers of the nodal device, the message 931 is upswitched 922 and a communicatively compatible internetwork version of the message, having the original message content addressed to a cloud host 1000 or hosts, is broadcast with amplification on a broad area radioset, such that it is picked up 924 by an internetwork portal and relayed to the administrative server 1000 of the system. The system evaluates according to rules and contextual information available to it, and actuates an alternate owner's device 911, either to deliver a notification or to cause local commands at home, at the “nest” site, or at a work location, to be executed. The sequence ends 928 when action has been taken. The owner's direct participation in the sequence is not required; but the input and outputs are logged and may be accessed by the owner from any device capable of accessing the administrative server. Thus the system acts as a personal assistant to the owner, taking care of issues that the owner may be unable to, or chose not to, personally attend to. The details of the action(s) taken are dependent on contextual information available to the administrative server 924 and any instructions and permissions set up by the owner.

While the owner's device is depicted figuratively as a smart device 911, any device capable of receiving digital commands may be operated and controlled in this way. In some instances, the smart device may have sufficient machine capability to execute a command without involvement of a peripheral 3000. For example, the smart device may be able to take a picture, or respond 925 by sending a location to the cloud host server, and so forth. Thus if the owner's response is insufficient because the device is lost, the cloud host may be programmed to command actions that will assist the owner in finding it. Numerous examples may be given of uses for the systems of the invention.

FIGS. 9A, 9B and 9C are plan and perspective views of an exemplary radiobeacon 600 configured for use in the inventive systems and networks. FIG. 9A identifies a radiobeacon with disk-shaped body, an edge-mounted button switch 614 a, and a cord orifice 617 such as for securing the radiobeacon to a keychain or to an object in need of monitoring. FIGS. 9B and 9C are illustrations in perspective showing front and back features of a representative radiobeacon device 600. Incorporated by reference is U.S. patent application Ser. No. 14/301236 titled “Tracking Device System”, where further description is provided.

The radiobeacon 600 is an assembly having outside clamshell housing pieces 611, 616. The covers are made of glass filled acrylonitrile butadiene styrene (ABS) thermoplastic which is light in weight, can be injection molded and is resistant to impact, heat, water, acids, alkalis, alcohols and oils. The housing typically is partially translucent, and permits light to enter and exit one or more surfaces. The top and bottom clamshell housing pieces 611, 616 have circular-shaped bodies 603 a, 603 b, each with an annular wall 604 a, 604 b. The covers also form a through-hole 617 for receiving a cord or chain to attach the radiobeacon to an object, a pet or the clothing of a person. Sealing bung 605 inside the cord hole 617 prevents moisture from entering the internal cavity inside the radiobeacon housing. This is a vent for assembly and is closed after the body is sealed shut.

Multifunction button 614 a is operable to perform one or more functions according to context and history. The button operates with one or more control programs resident on a host device during setup of alarms, to pair triggers, and if so enabled, to remotely control operations of the host device.

FIGS. 10A and 10B are exploded views of an exemplary radiobeacon. The radiobeacon 600 is an assembly having outside covers 611, 616. The covers are made of glass filled acrylonitrile butadiene styrene (ABS) thermoplastic which is light in weight, can be injection molded and is resistant to impact, heat, water, acids, alkalis, alcohols and oils. The top and bottom clamshell housing pieces 611, 616 have circular-shaped bodies 603 a, 603 b, each with an annular wall 604 a, 604 b. The covers also form a through-hole 617 for receiving a cord or chain to attach the radiobeacon to an object, a pet or the clothing of a person.

The clamshell pieces 611, 616 enclose a printed circuit board (PCB) 612 and a battery 615. The PCB 612 has a crescent-shaped body with an outer edge 602 a having a radius of curvature slightly smaller than the radius of curvature of the covers 611, 616 and an inner edge 602 b with a smaller radius of curvature. Two circular arcs of different diameters thus define the crescent shape of the PCB 612. The PCB 612 has an opening 613 a for receiving a circular battery 615.

The diameter of the battery 615 is smaller than the diameter of opening 613 a in the PCB 612. The battery 615 has one terminal on its surface and another terminal on its edge. The edge of the battery engages a conductive edge connector 618 on the inner edge 602 b of the PCB 612. Another conductor has a spring-biased body 619 that extends from PCB 612 toward the middle of a surface of the battery 615. The battery 615 is held in the opening 613 between the two covers 611, 616 and against the conductive edge connector 618 on the inner edge 602 b of the PCB 612.

Bottom housing piece 616 has an opening 613 b sufficient to receive the battery 615. A threaded battery cover 608 a, a matching threaded annular wall 608 b and an O-ring 607 secures battery 615 in the openings 613 a, 613 b. A detent 609 in the surface of the battery cover 608 receives an opening tool, such a screwdriver or the edge of a coin (not shown). Inserting the tool in the detent and rotating the cover 608 a open the cover to access the battery.

The radiobeacon is assembled by inserting a PCB 612 with component circuitry on the inside surface of housing base piece 616. The top housing 611 is placed on top of base 616 to define a cavity that holds the battery 615 and PCB 612. The two covers are ultrasonically sealed to resist water or other materials from entering the device 600. A battery is inserted through opening 613 b in cover 616 and the battery lid 608 a sealedly engages O-ring 607 and threaded wall 608 b. Cover 608 a rotates in opposite directions to close or open. By encircling the battery with the printed circuit board 612, the thickness of the assembly is not increased, and us determined only by the separation of covers 611, 616 and the thickness of the battery 615. Some embodiments are 5 mm thin and 40 mm in diameter. Unlike other devices that use batteries, the PCB does not contribute to the thickness of the device 600 because the battery 615 does not rest on the PCB 612 but is partially encircled by the opening 613 a in the PCB 612.

A multi-function button 614 a extends from an opening defined by half-oval walls 614 b, 614 c in the sidewall of the junction of the stubby cylindrical walls 604 a, and 604 b. In one embodiment there is a single multi-function rubber button 614 a that extends from the edge of the device. Button 614 a is held in place by wall edges 614 b, 614 c that overlap surface or “boot” 614 d to hold the rubber button 614 a inside the covers 611, 616. The rubber button is aligned with a mechanical switch 614 e that is attached to the PCB 612 and coupled to the core circuit.

The covers 611, 616 and the PCB 612 have aligned openings 617 a, 617 b, 617 c that create an external key ring hole 617 for holding a key ring, a carrying chain or cord. As will be explained below, the component circuitry has a speaker for sounding one or more alarms. The edge of the covers defines a key ring hole 617 that has on or more small holes that may be sealed. In those embodiments a removable rubber plug 605 is inserted into the hole to prevent moisture and water from entering the cavity holding the component circuitry 620. As an alternative, a larger rubber plug could fill the entire channel 617 a through 617 c or at least cover the annular inner surface of the keyhole.

FIG. 11 is an animation view showing a radiobeacon in three consecutive positions at times T₁, T₂, T₃. In each snapshot, the radiobeacon 600 transits a defined path (walking figure 1040, MOTION, dashed heavy arrow) so as to come into proximity with a series of three community nodal devices (1010,1011,1012). Each nodal device registers a message (1021,1022,1023) from the radiobeacon in turn and upswitchingly transmits a broadband message in turn (1031,1032,1033) to a cloud server 1000, which in turn may initiate a command transmission to a nodal device 911 in a remote location 1030. In this instance, the remote nodal device 911 relays the command to a remote machine 3000 for execution and monitors that the execution of the command was completed (double-headed arrow). The command might contain data for displaying a notification on device 911 to the owner of the radiobeacon 600 or to a friend having shared permissions. The smartphone 911 can report status to the cloud server: that the friend has acknowledged the notification and is trying to catch up with FIG. 1040.

Radio signals are indicated at three times T₁, T₂, and T₃, each corresponding to a point in time and a position in the right-to-left path of the walking FIG. 1040. Each message may contain updated sensor content reflective of time and distance travelled. The cloud host server may use this information to track the radiobeacon 600, which in this example is attached to a keychain that has been unknowingly carried away by an individual 1040 in a borrowed jacket. The messages may also include other sensor information, such as microclimate indicators, insolation, and direct or indirect indicators of proximity and location.

In some instances, permission may be in place to engage foreground services. For example, local nodal device 1012 may include a virtual machine accessory video camera either integral to the smartphone or separately linked to the smart device by a USB or wireless link such as a headband or a pair of smart glasses worn on the head of a community member. The video can then be streamed to the cloud, and according to user permissions in an administrative server, forwarded to one or more display stations or web sites to help track the errant keychain. This could be important when the person carrying the radiobeacon 600 has left their medications at home, or is missing and needs to be found. In another instance, the operator of radiobeacon 1012 could be invited to approach walking FIG. 1040 and offer assistance.

Roles may be reversed, nodal device 911 may interchangeably insert itself into ad hoc networks by proximity to the radiobeacons of others, and serve as a shared community resource—either way, all community nodal devices will reciprocate in upswitchingly transmitting data from a radiobeacon to the cloud.

Nodal device 911 may also function as a radiobeacon, or may signal the cloud server to request devices 1010, 1011 and 1012 report their location so as to track the person carrying radiobeacon device 600. Generally the messages are very short and result in a minimal load on the network. In other cases, some devices may have permission to permit sharing of foreground resources such as GPS location that can be used to track the keychain (or the missing person).

In some embodiments, the radiobeacon may carry its own GPS device and broadcast its latitude and longitude coordinates in the message (i.e., as a geostamp), accompanied by a timestamp. In other embodiments, the radiobeacon message may be stamped with the GPS coordinates of any nodal device that participates in systems such as shown in the preceding figures and is within an effective radio contact area of any radiobeacon. In still other embodiments, the location of one nodal device may be paired with the range of one radiobeacon 600. For example, in the system shown in FIG. 11, the nodal device 1012 provides a location using its GPS function and pairs that location with the proximity of radiobeacon 600 and the time of contact. These radiobeacons are sophisticated “radiotags” when attached to children, pets, property and so forth.

Where timestamps and geostamps can be aggregated, the host notification may include a tracking feature whereby a plurality of recent locations of said lost object are visually displayed in the form of a track over time superimposed on a map. The track may also include an extrapolation of at least one future position or a composite showing the locations of one or two friends who in position to intersect the track ahead of the lost object, thus potentially recovering it by activating a visual or audible alarm when in close range.

FIG. 12 is a schematic view of a system 1100 and network having three (or more) radiobeacons (1101, 1102, 1103), one smartphone 911 (with software “*”, 1002) with owner/user in proximity to the radiobeacons, a cloud server 1000, and an accessible database 1001 configured to store information about radio contacts, including identifier, location, zone and temperature and to display that in a dashboard display 1166 broadcast to smart devices requesting it. Radiobeacon 1102 is tagged to an item 1106 such as a child's pocket tag (or may be attached with a safety pin). An owner/user's smartphone 911 is in motion away from the radiobeacons and will soon be out of radio broadcast range of the low energy transmissions. However, the smartphone remains in radio contact with cloud host 1000, and has installed application (asterisk, 1002) for receiving radiobeacon sensor data from the cloud host.

In this embodiment, the cloud host server includes one or more administrative databases 1001 that keep records on owners, users, location and sensor data from each radiobeacon in the system. For user of the network 1100, the database 1001 would show a table 1160 of the devices owned by the user (or those devices for which the user had granted or received one or more privileges or are marked for public access), the identity (column 1161) of each device that is owned or subject to a privilege granted or received, the information (columns 1164, 1165) reported by each sensor of each device, including and not limited to the time the information was received and the location (column 1162) of the devices 1101, 1102, 1103. At any time the owner of the radiobeacons and nodal device 911 may view a report 1166 showing information on the location and sensors of each radiobeacon, including the last known location of the radiobeacon and when the last known location was recorded in the cloud administrative database 1001. Thus in a simple application, the owner's own smart device 911 can monitor radiobeacon 1102 as it approaches the limit of its broadcast range.

If the low energy broadcast range of radiobeacon 1102 from the owner's smart device 911 is exceeded as the owner walks away, no further information is received by the cloud host from smartphone 911. However, a number of other community nodal devices (1114, 1115, 1116, 1117, 1118) may be within radio range. If programmed to recognize the identifiers and message, the device will not discard the radio contact and message, but will instead upswitch the information in a wide area broadcast on a separate antenna to the cloud host 1000, in this case including the GPS location 1162 of “radiotag” 1102. The nodal device will forward the radiobeacon identity, sensor information, timestamp, and any GPS geostamp. As long as an application for sharing radiobeacon sensor data is running in background, each nodal device will upswitch any radiobeacon message from the radiobeacons. No permission is required to receive and upload the radiobeacon signal. The upswitch and retransmission of radiobeacon information by the nodal devices (1114,1115,1116,1117,1118) imposes no hardship on the shared resources of the system.

Thus if the child carrying tag 1106 is moving in the opposite direction (OBJECT MOTION) of a parent (OWNER′S MOTION) and is out of range, an owner of radiobeacon 1102 may access the database 1001 and mark the object (with radiobeacon tag) as “lost.” Assume another user carries nodal device 1115 and has no shared privileges for radiobeacon 1102. Nevertheless, when nodal device 1115 passes within range of the radiobeacon signal from radiobeacon 1102, the identity of the lost device 1102 and its approximate GPS location will be automatically relayed to the cloud host 1000 and recorded on the database 1001. The host will then prepare a report 1166 and forward it to the owner's smartphone 911. The report details the general location of the lost device; the location is periodically updated as the radiobeacon tag 1102 encounters other nodal devices, for example nodal device 1116. The approximate location can be displayed on a suitable application such as Google Maps, or MapQuest, to provide the owner with enough information to attempt to recover the device. As the owner gets in proximity, the owner's smartphone captures the signature ping from radiotag 1102 and can send a command that actuates the radiobeacon to sound an alarm or blink in the dark. Suddenly the exact location of the missing item is readily discoverable. Similarly, a child, discovering that he is lost, may press button 614 a to alert the system and initiate a response that involves establishing the child's location and reuniting the child with his parent.

A user can have an alert triggered when the distance or proximity between the nodal device 911 and the radiobeacon 600 exceeds a predetermined distance selected by the operator of the nodal device.

Radiobeacons of the invention may be provided with speaker and a light emitting diode so as to tag an object for later recovery. To execute a search for the object, any nodal device with appropriate permissions may command the radiobeacon to emit an alert, including a buzz or flashing light. If an objecting tagged with the radiobeacon is inside a drawer or under a pillow, the person searching for the object will hear the buzz or see the flashing light. The nodal device may also set automatic alerts triggered by increasing or decreasing distance between the radiobeacon and the nodal device, for example.

The radiobeacon message includes identification information specific to the radiobeacon (generally manufacturer's make and model) and may include sensor output representative of the status of the charge of the battery. The program displays both the range and battery status information. As explained above, the location of the radiobeacon may be detected by other nodal devices, which may assist the owner in locating a lost object to which a radiobeacon is attached. Accordingly, the nodal device, if associated with network of other nodal devices, may acquire information about the location of a radiobeacon from other networked nodal devices (any proximate nodal device owned by an anonymous user). This sharing is promiscuous and ad hoc. The control program provides a feature for selecting a map displaying the remote location of each radiobeacon controlled by the owner.

Each radiobeacon (1101,1102,1103) is registered by the cloud host to an owner (using the unique UUID) and may have one or more shared users. As used in this disclosure, the term “owner” applies to a user of a radiobeacon who has primary control over the radiobeacon. The embodiment envisions local, regional, national and international networks within the scope of “internetworks”. It also envisions registered owner-users of radiobeacons and other registered users all sharing a cloud host server or servers for collecting information about (and from) radiobeacons globally, or in a particular local area. An owner-user may grant one or more privileges to other users who are defined in the administrative database 1001 as “friends”, so that the system will allow friends some level of access or control of the owner's radiobeacons and sensor output. For example, one owner-user may give a friend a privilege to view all data in a host database 1001 or webpage (or view data only associated with a selected subset of radiobeacons chosen by the owner-user for sharing). Even when the owner permits other users to see the data, some data may be marked “private” and excluded from the view of the shared user. An owner may also permit other users to control one, more, or all functions of individual radiobeacons of the owner. An owner may also allow device data to be posted publicly, so that any user can view the data.

The friend feature solves a potential problem of locating lost radiobeacons. If a friend finds a lost item of an owner by encountering a radio signal associated with the tag (such as tag 1102), the friend may discretely notify the owner that the friend has found the lost radiobeacon (and by extension the object 1106 attached to the device) by calling the owner or sending the owner an email or text message. The email could include a map with a pin showing the location.

In an alternative friend-based scenario, assume a user of nodal device 1115 (who was granted privileges for the lost radiotag 1102 by its owner) detects the lost device. The owner sees on the database that the user of nodal device 1115 is close to the lost radiotag 1102 and also has privileges on it. The owner may then contact the friend/user via telephone or email and ask the user to find the lost radiotag 1102 by initiating a sound or light alert while in proximity. The missing item 1106 is then easily found by sight or hearing.

Shared use has a number of advantages. For example, assume the owner of the radiobeacon 1101 is away from home and receives a call from a member of his family asking for help finding a lost object such as a pistol tagged by a radiotag. The owner could log into the cloud host server 1000 and send a suitable command to the radiobeacon 1101 to operate an internal speaker and LED. Perhaps more easily, if the owner had shared control of the radiobeacon with other family members, then the shared user could send the command to generate an audible “homing signal” directly. Objects lost anywhere in the world may be located by using position data provided by other nodal devices that carry the application and are registered to the cloud host administrative site 1000.

The database has numerous uses. Radiobeacons may be distributed over a large geographic area where each radiobeacon is periodically in contact with the cloud host as it makes radio contact with passing nodal devices. The radiobeacons may be installed at one or more known locations or may have been located by some mapping means when installed. The sensors on the radiobeacons will report their sensor package data, such as temperatures, air pressure, humidity, and other environmental characteristics, thus providing in aggregate a detailed local picture of the weather in a geographic area. Databases 1001 may include maps, tables, place names, or zones 1163.

Sensor data may serve as a trigger signal. There are virtually an unlimited number of sensors that can be used to provide trigger signals and a similar unlimited of responses or alerts that may be given in response to any trigger signals. Each radiobeacon may have a button 614 a and may have one or more sensors as described earlier. The button and each sensor may generate a trigger signal. Trigger signals may be combined in any number of combinations and/or sequences of trigger signals to generate particular trigger signals depending upon the occurrence of predetermined combinations and/or sequences of trigger signals. The radiobeacons and nodal devices may thus also generate one or more unique responses or alerts upon receipt of any designated trigger signals and unique combinations thereof. Multifunction buttons and keypads may also be used to aid in programming and organizing notifications, triggers, and executable functions.

FIG. 13 is an exemplary view of a system 1200 and network having three radiobeacons (1201, 1202, 1203), a nodal device (identified here as a “hub” 1204), an optional computing device 1205, a cloud-based cloud host server, and three client devices. Radiobeacons (1201,1202,1203) are in wireless communication with hub 1204. The hub 1204 may be connected to a gateway computing resource 1205 that in turn is connected to the cloud host 1000. In some embodiments, the hub 1204 is directly connected to the cloud, bypassing optional desktop computer 1205. The hub 1204 listens for signals from the radiobeacons. The hub has a bluetoothed radioset or other wireless communication apparatus and can sense the range of each radiobeacon within its effective field. Upon receiving signals from one or more radiobeacons, the hub relays any sensor payload and identifier information associated with the radiobeacons to the cloud host server. Likewise, the hub may send control information received from the owner via the cloud host server to each or all the radiobeacons. For illustration, reports and updates may be sent to a remote computer 1210, a tablet 1211, or a user's smartphone 1213. Similarly, the smartphone, tablet or computer may be used to send commands to one or more of the beacons via hub 1204. Commands received from the host are downswitched to a bluetoothed compatible antenna at a frequency in the Bluetooth band for transmission to a radiobeacon having the transceiver feature described in FIG. 7B. Internet client 1205 (shown here as a desktop computer) is optional if hub 1204 is equipped with a wide area transceiver communicatively compatible with an internetwork portal.

These embodiments of networks rely on integrate multiple radiobeacons and bluetoothed devices into an ad hoc network by providing an application configured to switch bluetoothed radio signals to a higher powered internetwork and in reverse, from an internetwork to a short range bluetoothed signal. In this way, a nodal device (e.g. a smartphone) does not have to directly control the radiobeacons, however. All radiobeacons for an owner are registered in the hub 1204 and each can be securely accessed from a smartphone or other nodal device anywhere in the world. The registered radiobeacons can be used for home security, automation, or playing games with friends across the world, for example.

FIGS. 14 and 15 are views of an alternate system and network architecture of the invention. The system includes a radiobeacon 600 and an accessory “beaconmate” 1300. In this case, the radiobeacon is “radiotagging” a key 1370. The beaconmate 1300 is in bidirectional short range communication 1310 with the radiobeacon 600. Whereas the radiobeacon has only a single button 614 a, the beaconmate has buttons 1301 a through 1301 n, and includes a special function bar 1303. Also included is an LED rose 1304 with eight compass pointers 1309 and a central “enter” button 1305. Center button 1305 is context sensitive, and for example can actuate a directional search on a first press and an audible homing signal from a misplaced smartphone (if equipped with a compatible application package) on a second press, thus aiding users in finding a phone before losing a call.

The buttons appeal to users less familiar with a gestural language to differentiate a lexicon of commands, and is less expensive to implement than a voice recognition system in the limited computing power environment of battery operated devices.

The beaconmate device can also include a flashlight 1306, a compass with individually illuminated LEDs (1309) that function as directional indicators in search mode and as capacitive switches in navigate mode. Also included in this embodiment is a detachable memory stick that when inserted into a USB port in the beaconmate, becomes the base flashlight 1306. Flashlight 1306 lights when button 1305 is held down. The device may also include a solar recharger (or RF recharger as described earlier) and a disposable battery power source. This device may alternatively have a retractable USB connector and may be plugged into a cellphone for setup of user functions in on-board flash memory.

In other embodiments, the flashlight/memory stick may be pulled out to expose a USB miniconnector, which would otherwise sit in a water resistant cavity and be electronically connected via a databus to the circuit board and processor inside. Because the device as so configured is capable of both bluetoothed and USB connectivity, added levels of function are achieved. The user would plug the memory stick into a phone, actuate bluetoothed pairing, transfer all the needed configuration information while operating in bluetoothed mode, and then plug the memory stick back into the beaconmate receptacle, where the setup configuration would be accessed during operation of the device. Removing the memory stick would render the device unworkable. Alternatively, the memory stick can be used to store photos from a smartphone, and then plugged into a computer or camera for further processing and archiving.

FIG. 15 is a view of a simplified command and control system utilizing beaconmate 1300, radiobeacon 600, nodal device 911, a cloud host 1000, and remote actuation device represented by smartphone 25. In this embodiment, the beaconmate and the radiobeacon are in radio contact with the nodal device, but the beaconmate adds the power of bidirectional communication with the host device. Using this system, the beaconmate may be configured to provide an alternate interface with button shortcuts for accessing functions of the smart device 911 and for triggering remote actuation of other machines and devices 3000 via cloud access to functions in actuation device 25.

FIG. 16 is an exemplary view of a system 1500 showing radiobeacon 600 with beaconmate 1300 in digital communication with a smartphone 1501 in local area proximity (represented by box 1505). Here a second smartphone 1502 initiates a call to the first smartphone. The call recipient 85 may have set down the phone and instead relies on the beaconmate to report and respond to the incoming telephone call according to pre-programmed rules. The keypad may be color coded to indicate whether the user knows the caller by the color of the key that lights up. The beaconmate can also be set up to send a signal to the beacon, triggering a sensor dump, in which the beacon reports any sensor data that provides needed context, a sort of “do not disturb” such as accelerometry indicating the call recipient is driving. In this way, beacons may be given enhanced functions. Beacons having one or more sensors may be supplemented, for example, with additional sensors mounted in the beaconmate. By using very low signal strength 1311 to communicate from the beaconmate to the radiobeacon, longer battery life of the accessory 1300 is achieved. Bold arrow 1311 represents ultra-low energy radio transmissions or “messages” between the radiobeacon 600 and beaconmate 1300.

FIG. 17 is an exemplary schematic view of a beaconmate 1300 (dashed box) in direct digital communication with a nodal device 1501 at close range. Signals received by the nodal device are transmitted to a cloud host 1000, analyzed according to user-programmed rules and commands, and from there to a client device 911. A smartphone is represented but is to be indicative of any compatible nodal device, shown here displaying a map.

Components identified in this simplified block view include a bluetoothed low energy (BTLE) core device 1350. The core device includes an antenna for sending low energy radio signals 1312. The core device generally includes an integrated microcontroller, read only memory (ROM), random access memory (RAM) sufficient to support rudimentary control, or may be provided with firmware sufficient for basic functions. For some applications, a removable flash memory device may be incorporated. The memory device may be added through a slot in the outside walls or may be installed under the battery. The memory device may tabulate data collected by sensors mounted in the device for later retrieval and analysis.

The core device 1350 has a clock. The radiobeacon signal and any signal from a sensor may include the time any message or signal is sent. According to an application subroutine (such as a near field communications sensor unit), nodal device 1360 may wake the device 1300, receive sensor output, and then set the device back to sleep such that its broadcast signal is only active when the two units are in close proximity. A second nodal device 911 may again later wake up the radiobeacon and receive a signal. The core device also tracks time and any alert may be paired to one or more chosen times or day, week, month or year.

The core device 1350 is assigned a unique identification code (UUID) and will generally broadcast at periodic intervals as programmed by the developer. Broadcasts 1312 may be made using a ceramic antenna, a loop antenna, or a dipole antenna selected for low energy consumption.

The core device 1350 controls a speaker 1323 and an array 1304 of light emitting diodes formed as a compass rose as a navigation and tracking aid. The speaker 1323 and the LED “rose” array 1304 are configured to communicate alarms directly to a user and to assist in tracking and locating lost items, among other functions.

The core device 1350 is connected to one or more sensors (1340,1341), or any number of sensors 1349 (SN). Exemplary sensors sense environmental and physical parameters experienced by the radiobeacon, including and not limited to temperature, light intensity, smoke, voltage, sound, motion, displacement, acceleration, humidity, pressure, radiation, button-press event, compass direction, or to report daylight levels, traffic levels, noise levels, NOX levels, and unusual noises such as gunshots or sirens, or self-reporting, such as reporting a low battery level, or other stimulus, sensor data, or environmental parameters, without limitation thereto. In some embodiments, a sensor is a combined multi-axis motion sensor and temperature sensor. In one embodiment, the sensor has an accelerometer, a gyroscope, a compass, and a magnetometer for each axis. The information or “sensor data” output by the multi-axis motion sensor enables the receiver (i.e., a host device such as a smartphone) to monitor and track the beaconmate (which is radiotagged by a radiobeacon) as it moves from one location to another. Alternatively, the beaconmate may include a GPS-based location sensor. The motion of the device can be monitored continuously by a cloud host server 1000 as long as the receiver 1360 is close enough to be in wireless contact with the sensor package on board or alternatively with a radiobeacon in wireless contact with the beaconmate. As an alternative, the information may be stored in a memory in the device and accessed later.

Some embodiments of the beaconmate of the invention are equipped with rechargeable batteries 1325 that may be recharged via an inductive charger 1326. Wireless chargers, also known as induction chargers, typically place one coil in a charging device or pad that is connected to an AC power source. Battery top off controls and discharge controls are known in the art and may be implemented where warranted.

Other embodiments of the invention may have wired rechargers. These are well-known devices and may be incorporated into beaconmate devices of the invention by providing a suitable port (not shown) to receive power from an external power supply. However, such external ports provide openings in the housing that are not desirable, and hence indirect charging means are preferred. A disposable battery 1320 may be included.

Other embodiments may have solar power cells and chargers 1327, so that battery 1325 is rechargeable by exposure to light. Solar cells have a dual role by acting as light sensors. This allows flexibility in configuring notifications to the user by pairing sensor data and other contextual data to the presence or absence of light. The amount of current generated by the solar cells is indicative of the intensity of the light falling on the beaconmate sensor.

While not shown, other embodiments of the beaconmate have antennas and circuitry for harvesting RF power to recharge battery 1325. RF harvesters having a GMS antenna, one or more resident circuits, boosters, peak detectors, and an adder, are known in the art. The circuit contains passive components and is designed to have tuned circuits at known frequencies of cell phone towers (960 MHz) and bluetoothed devices (2.4 GHz). The boosters are Villard voltage multipliers. Reported test results show the RF harvester located within five hundred meters of a cell tower was capable of generating 0.16 microWatt and successfully operated a calculator and a light emitting diode. Related advances include Dickson cascade diode capacitor circuits, charge pumps, Karthaus-Fischer cascade voltage doublers and rectantennas known in the art.

Actuation device 911 may be a smartphone or pad for displaying a map as shown. The map may be an interactive map and may include a voice overlay or data overlay. Maps may include aggregate data, such as traffic, radio traffic, tremors, fog, crowding, or special offers, sites of interest, meeting places, and so forth.

FIG. 18 is an alternative system and network having a radiobeacon 600, a beaconmate 1300, a smartphone 1501, and a cloud-based cloud host server 1000. Commands issued from the host platform 1000 may be directed using one of the buttons on the beaconmate, such that various pre-programmed responses are selectable with a button press depending which button is pressed and on context. Other responses may be selected with a combination of button presses. The radiobeacon periodically pings the user's phone and a notification is generated in the beaconmate if the phone 1501 is no longer in very close proximity. In an improvement over the “hot-cold” proximity sensors of the art, direction pointers in the LED rose 1304 will light up according to the last known position of the phone. In this way, the user need not carry the phone directly on his person, and will be reminded if he moves too far away from the phone and could miss a call.

Similar networks may be set up for controlling remote machines. In one exemplary variant, a user may press a button on the beaconmate to remotely take a photo, such as a “selfie”, with his cellphone 911. In another variant, the beaconmate buttons may be assigned functions, such as opening a garage door, tracking a child, or calling a particular friend. The beaconmate may illuminate particular buttons or colors of the compass rose according to who is calling. Also, the beaconmate may receive reports of a low battery in either the radiobeacon or the phone and may cause a message to be initiated and displayed on the phone to the user before power levels become critical.

Thus the beaconmate is an extension of the radiobeacon and is an improvement over embodiments having only a single button 614 a. More complex systems can be conceived. The beaconmate may also include voice actuation commands and may do mathematical problems like adding, subtracting, or calculating mortgage payments from principal and interest rate by voice commands. The beaconmate has a program that allows the user to create custom trigger signals including combinations and/or sequences of individual trigger signals, thus serving as a personal assistant while being small enough to be pocketed or pinned to a lapel.

FIG. 19 shows a view of a message in which bit overloading is used to transmit sensor signals. Advantageously, because the data is highly compressed, typically a few hundred bytes or less per transmission, the load on the network is minimal. Thus a network may include more transmissions per unit time, but because each transmission is a flickering transmission, the network is not slowed significantly by the increased radio traffic. Rather than collect sensor data by asking the host to perform top-down queries, the sensor data is promiscuously uploaded whenever an opportunity presents, and the cloud host works with messages as they are received. This simplifies the organization and execution, leading to improved resource efficiency through sharing.

Sensor data may be overloaded into messages in “first sensor value” and “second sensor value” frames within a standard communications protocol. The formatting is configured to be compliant with a low power packet communications format (without disrupting the underlying protocol) but contains encoded sensor output from a sensor unit associated with the originating radiobeacon. These messages may be upswitchedly transmitted in a broadband communications protocol to a cloud host that is competent to decode the sensor data.

In order to conserve bandwidth and to ensure unambiguous transmission of sensor data from the radiobeacons, framing of signals and loading of the sensor data is performed. The loading function may be performed by an encoder associated with a radio emitter or may be performed by software executed in the emitter module or by a processor associated with the emitter. The signal broadcast by the radio is generally packeted or otherwise configured to contain an identifier value (UUID), and one or more frames of the message, where, in part at least, output in digitized form insertedly encoded in one or more standard frames of a communications protocol as describe above. Thus the encoder function (see for example 80 b, FIG. 7B) may be a stand-alone circuit operating to configure the radio signal or may be integrated into either the processor or the radio emitter if desired and may be implemented using software or firmware or a combination of both.

For overloaded transmission message 1800, both the first frame 1802 and the second frame 1805 are split between static conventional data and dynamic sensor data. UUID broadcast 1801 is followed by a split value in which the protocol allows four reserved bits 1803 for owner-specified information such as location or direction and up to twelve reserved bits 1804 for a digitized dynamic output from one or more sensors. Similarly, a next frame may contain eight reserved bits 1806 for beacon naming and eight reserved bits 1807 for dynamic sensor data. Some frames may be termed “major value” and “minor value” and may be overloaded with sensor data as described here. The message with reserved bits may be read by the processor, may be written to memory, or may be upswitchedly transmitted onto a cloud host in a broad area network. Reserved bits may be selected from least significant bits or most significant bits, or may be reserved bits at any point in the frame. For example, bit 1808 may be high or low as indicative of whether a switch is open or closed. In this way sensor data is overloaded on transmissions while complying with standardized radio communication protocols so as to minimize cost to the system for implementation.

FIGS. 20A and 20B are representative views to illustrate screenshots of graphical user interface displays generated by an exemplary software application of the invention as displayed on a nodal device or other computing machine, here represented by a common smartphone screen.

FIG. 20A illustrates a first screenshot 1900 a. The application is operative in cooperation with a cloud host in managing a radiobeacon notification system. A setup routine detects radiobeacons indicated by icons 1902, 1903 in the vicinity and offers the user tools to monitor and configure the rules and privileges associated with each radiobeacon. Radiobeacons may be physically attached to objects of interest by the owner; a process termed here “radiotagging”. The cluster of radiobeacons 1902, 1903 on defines a hive (icon, 1901) administered by a hub. The screenshot illustrates how to configure the hive. In the top banner 1906, shown are control buttons 1907, 1908 and 1909, respectively, for enabling the smartphone to receive and send bluetoothed transmissions, for releasing one or more of the radiobeacons from the hive, and for setting a toolbox of settings for the radiobeacons. Banner 1910 defines columns for active devices 1911, their range 1912, and their status 1913. For example, radiobeacon 1902 (icon TD1) has a range indicated by three bars and a status showing a can icon 1914. In the next row, another radiobeacon 1903 (icon TD2) with signal bars and can 1915. The can icon is used to indicate that the radiobeacon is under the owner's control but can be released if so desired.

In the hive there are several more radiotagged objects below the banner titled “Far away” (1520). These radiobeacons are not within range of the low energy radioset. The faraway objects include My Wallet 1904 and another object named “cat” (1905). The cat is networked (icon 1521) to indicate that the radiobeacon physically linked to the cat's collar is shared with another user.

Near the bottom of the screenshot, banner 1522 shows “Friends”. A friend is any other user who has some control and shared access over one or more of the radiobeacons. The icon 1523 may be pressed to add new friends. Also shown are existing friends, as may be updated by pressing any of the buttons in the row.

The computer program enables the nodal device to detect radiobeacons within range of the nodal device and acquire control of the radiobeacon unless another nodal device already controls the device. The nodal device may also release from its control one or more selected radiobeacons. The control program also allows the user to keep private the information of the tracking device. Once set to private, only the nodal device or other designated apparatuses or individuals will have access to data from the radiobeacon.

The control program allows the user of the user to select at least one alert. The nodal device or the radiobeacon or both may generate the alerts. In order to trigger the alert, the radiobeacon broadcasts a radiobeacon signal via a bluetoothed transceiver.

In a preferred embodiment, range is a trigger for the radiobeacons. On the nodal device the user may define one or more ranges for generating responses including alerts. One potential use is keeping a parent advised of the relative location of a child while shopping in a store. Different responses or alerts could be given at different ranges as the distance between the child and the parent varies. When used with a hive, a trigger may be given when a radiobeacon leaves or enters the hive.

The signal strength of the radiobeacon signal received by the nodal device is representative of the distance or range between the nodal device and the tacking apparatus. The signal strength is considered a condition for a distance alert. If a nodal device suddenly receives a radiobeacon signal of a controlled radiobeacon, the nodal device may indicate the device has returned to a location proximate the nodal device. Likewise, failure to detect a radiobeacon signal of a controlled radiobeacon indicates the device is outside the range of the nodal device. The relative strength of the radiobeacon signal is proportional to the proximity between the nodal device and the controlled radiobeacon.

The nodal device or the radiobeacon or both may monitor other conditions. Each other condition and combinations of two or more conditions may be paired or otherwise associated with each other to provide multiple conditions for triggering an alert. In addition to the range signal radiobeacon, the radiobeacon may carry one or more sensors and each sensor may output one or more signals representative of other conditions monitored by the sensors. Other conditions include and are not limited to motion of the sensor in any direction or in a particular direction; temperature and other signals representative of time, the geographic location of the radiobeacon or motion and other physical, biological or chemical conditions being monitored by sensors. As such, each condition monitored may be associated or paired with any other one or more conditions to provide multiple conditions that must be met to trigger an alert.

Time of day may be combined with other trigger signals to enable or disable one or more alerts, such as enabling a motion alert during the night but disabling the alert during the day. Other trigger signals and their combinations and/or sequences are possible with added sensors. The radiobeacons of the embodiments of the invention may use any of a vast number of sensors including and not limited to sensors for motion. Distance, velocity and acceleration, temperature, pressure, magnetic fields, gravity, humidity, moisture, vibration, pressure, light, electrical fields, ionizing and non-ionizing radiation, cosmic rays, and other physical aspects of the external environment; analytes for chemical or biological substances including and not limited to sensors for detecting toxic compositions such as carbon monoxide, carbon dioxide, methane, and other hazardous or poisonous components. The radiobeacons may be worn as badges by personnel to detect ambient analytes and physical parameters. The data collected by the radiobeacon may be sent to the data collection center of a cloud host 1000 where others can analyze it and provide responses or alerts to the personnel wearing the radiobeacons.

FIG. 20B is a screenshot 1900 b representing an exemplary graphical user interface for reporting locations of radiobeacons superimposed on a physical map of a defined area as displayed on a typical smartphone. The map can be zoomed in or zoomed out. Objects associated with a particular radiobeacon by an owner of the radiobeacon can be reported as lost to the cloud host server and if the radiobeacon identifier is detected by one or more other nodal devices, the cloud host server generates a map for the owner showing an approximate location of the device, for example as a set of GPS coordinates and a thumbtack centered over the objects likely location.

A top banner indicates an exit to a home page (icon 1952), and an indicium 1902, indicating that the display relates strictly to radiobeacon TD1. Indicium 1956 shows battery strength for the radiobeacon in percent; indicium 1907 is the release control command, and 1909 opens a toolbox of advanced user settings for configuring the radiobeacon. The next banner shows leftmost an indicium 1960 which when touched with immediately sound the audible homing signal for locating the radiobeacon when lost. The speaker in the radiobeacon will sound intermittently until the user finds it. Similarly, the indicium 1962 when touched activates an LED in the radiobeacon, making it easy to find in a darkened room or at night. Light is strobed periodically to help the user find the missing radiotag. If the radiobeacon is equipped with a vibrator, another symbol would be shown to activate the vibration. Triangular icon 1990 takes the user to a screen with options for setting alerts. The user may select the kind of alert (audio, light, vibration) and may pair the alert with contingencies such as distance or motion. Remote control may also be established between the smartphone and the radiobeacon. As explained above, a radiobeacon may control the smartphone and vice versa. If desired, the user may have an alert show up on the user's smart phone under one or more conditions. The user may operate a loudspeaker on the radiobeacon. The user may also for example set an alert when the battery is low. Other alerts can be set for separation distance of the radiobeacon and the smartphone. Controls will also configure the multi-function button, allowing the user to remotely operate the camera of the cellphone, or to send a pre-determined email or message by the press of a button. Further alert settings may depend on conditions such as location pairing. In this case, the alert is conditional and occurs only when the radiobeacon is at home, such that other alerts apply when the user is at work. Locations are identifiable by latitude and longitude and by range.

Icon 1964 is a map pin. Touching the map pin changes the screen shot from a range grid to a physical map 1967. The map includes a map pin symbol 1968 showing the approximate location of the radiobeacon 1902. The location is acquired from other nodal devices in its vicinity by sharing resources as described above. In the lower banners, icon 1968 again indicates shared control or access to a particular radiobeacon. Icon 1970 allows the user to quickly post a lost device on the cloud host. Selecting symbol 1972 marks the TD1 radiobeacon as private and only a privileged user may see the data generated from TD1 as well as the location of TD1. Data may be encrypted by the encoder as needed. Encrypting means are described for example in U.S. Pat. Appl. Doc. No. 61/892,178 titled: “Beacon Obfuscation by Time Based Association Key” which is incorporated herein in full by reference. Other encryption methods are known in the art. Symbol 1974 allows the user to release all control of the radiotag TD1. At that point, the radiotag TD1 may be claimed and controlled by any other authorized user. The bottom banner 1976 indicates other users with whom the current user has shared TD1.

Radiobeacon embodiments with a nine-axis temperature sensor package may be used to pair location, time, temperature, direction, and position, velocity and acceleration in each of three directions. For example, a user could set an alert to show whether the speed of a radiobeacon 1902 exceeded a threshold of ten miles per hour in the time between 10 AM to 11 AM on Aug. 4, 2014, when the temperature was between 75-85° F. while traveling north (0-90°) within the city limits of Seattle, Wash. As such, motion, time, temperature heading and location may all be paired together or in any combination of one or more types of sensed information to set an alert. The pairing of radiobeacon 1902 with a smartphone having GPS has endless possibilities. Motion data can be configured to user-defined alerts that include activating the speaker and LED. For instance, if a user was jogging and his speed dropped below a threshold, the speaker on the radiobeacon would buzz. In another embodiment the radiobeacon monitors temperature outdoors, and buzz from speaker accompanied by a notification on a smartphone could warn the user when the temperature dropped below a level that would harm outdoor plants.

In some embodiments the 9-axis sensor enables the systems of the invention for gestural control of functions of nodal devices. A program application installed on a nodal device records motion of a radiobeacon and associates the recorded motion with a function of the nodal device. With the application installed and running, the nodal device records a motion or set of motions of the radiobeacon such as a gesture. In other application-driven uses, a user may map out specific locations, click the button and the radiobeacon will save the place of interest. For example, a surveyor could walk a specific path, and mark specific points of interest such as corners of a road, or edges of a hill. The geographic properties of each point of interest would be saved and mapped out. Thus, the radiobeacons when used with systems and network architectures of the invention have uses in the fields of gardening, home security, child monitoring, health/fitness, sports applications, navigation, commercial and industrial monitoring and safety appliances, while not limited thereto. Further examples are as follows.

Example I

In a first example, a radiobeacon is positioned inside a passenger vehicle while the vehicle's owner runs a few errands. A sensor unit delivers data to a processor in the radiobeacon. If the internal temperature in the vehicle rises about a comfort level of perhaps 28° C., the radiobeacon will task itself to encode the most current temperature reading into bits 22-23 of a 26-bit data value. This will be broadcast following a distinctive radiobeacon message preamble. Any competent nodal device (having the needed software) that is owned by any anonymous community user in proximity to the radiobeacon (or one owned by the radiobeacon owner) will detect the message transmission. An application installed on the device will wake up when it recognizes the characteristic signal qualities and will upswitchedly transmit an amplified data packet to an internetwork compatible radioset and radio protocol and transmit that temperature data along with any unique identifiers to a cloud host that performs data validation and accesses instructions as to how to respond, what notification to push to the beacon owner's smartphone or other nodal device, and any other actions appropriate to the context. For instance, if the temperature rises to 35° C., the cloud host may be configured to make a notification to an emergency response number by telephone, using an electronic format or a voice synthesizer. The host will ask the emergency responder to press “one” on a keypad to acknowledge that first responders have been mobilized, and will then again notify the owner of the radiobeacon, this time that an emergency response is on the way. The redundancy provided by crowd-sharing a switching capability to send the radiobeacon output to a cloud host server ensures that a stepwise and effective response is achieved, even if the owner of the vehicle is unable to receive a notification (perhaps because the distance exceeds the 150 feet or so that the radiobeacon can transmit, or the owner's smartphone is shielded by structures that block the signal). In this way the owner of the radiobeacon is shown to be acting responsibly and can withstand scrutiny if a child or a pet is left in a locked vehicle without an adult in attendance for a short period of time. Nodal devices lacking the application typically will discard the data packet. But community users having the application will share a limited set of background resources with the owner of the radiobeacon, ensuring the safety of children and pets. Thus a limited sharing of resources achieves a greater benefit, and the system reciprocates by providing the same service if the role of owner and passerby is reversed. Anonymous users may be incentivized as needed to download the application from a distribution server associated with the cloud host, thereby becoming a community member.

Example II

In another example, by dynamically sharing resources provided by anonymous users as described in Example I above, an owner of a vehicle having a radiobeacon can receive a notification from a cloud host when the signal from the radiobeacon is lost due to excess distance or shielding that obstructs the signal. By configuring a radiobeacon with an accelerometer package, the radiobeacon can be triggered to encode and broadcast a signal if the vehicle is shaken such as by a car door opening or a broken window. Again sensor data is encoded and attached to the radiobeacon ping so that a message is transmitted that can be received by the owner's device or by an anonymous user's device. Under one circumstance, an owner's nodal device will intercept the broadcast signal and, using foreground resources in the nodal device under control of an application designed to receive and assess the data packet, push a notification onto the owner's nodal device, perhaps also disabling the vehicle's ignition system. Simultaneously, in background, any community members in radio proximity will receive the same broadcast signal and upswitch the signal to a cloud host. The cloud host will resolve the owner's address and according to notification policies, send a notification to the owner. First responders may also be called to the location, according to context. This redundancy ensures that the owner will be notified even if outside the radio transmission range of the beacon. The kindness of strangers in sharing resources becomes a valuable tool for avoiding injury or loss and is reciprocated between all community members. Surprisingly, passersby may not even know they have assisted.

Example III

Using essentially the system as described in two preceding examples, an owner mounts a radiobeacon on his front porch, above the door jamb. The radiobeacon is provided with a sensor package that includes a photocell, an accelerometer module with temperature sensor, an infrared motion detector, and a microphone with signal pattern analysis capability. Sensor data is routinely buffered in the radiobeacon and periodically encoded in a message that is preceded by a radiobeacon-specific preamble when transmitted. Transmission is made using a low-energy radioset. When at his residence, any message will be received by the owner on a smartphone or other device and notification will be made according to rules established during setup of an application designed to recognize the message and decode the sensor data, adding context as needed. Notifications will be made using foreground resources, waking up the device and the owner as needed. Under other circumstances, when the owner is not home, transmissions will be received at random by any proximate user carrying a compatible device and will be switched over to an internetwork-enabled radioset for transmission to a cloud host. Thus if the sound of a gunshot is recognized by the sensor package, the radiobeacon will be triggered to encode a data packet and will transmit a message using shared resources provided by any ad hoc anonymous users (perhaps the neighbors' smart device) to the cloud host, where the data will be analyzed and actions taken. A notification may be made to police responders, but also may be made to all anonymous users in the area (such as the neighbor), thus propagating the value of the information to multiple users, not merely the owner of the radiobeacon. So where neighborhood watch groups have been formed and members of the organization have installed the application and registered with the cloud host, a stronger level of cohesive local response is achieved in concert with the response by police, resulting in a higher level of public safety and an increased number of witnesses.

Example IV

Radiobeacons in a typical distributed installation with anonymous owners will likely not have overlapping radio contact. While installation in a single retail location is achievable, larger urban tracts generally cannot be united into a low energy radio network because of gaps in radio coverage. Thus a nodal device sharing a local radio signal area is needed to switch bluetoothed signals onto a broad area network. In some instances an owner's nodal device may perform this function, in other instances promiscuous, dynamic radio contact is made with the smart devices of anonymous users, literally passersby, providing an opportunity, when used with a compatible dual network device, to switch messages to the broad area network without cost to the anonymous user. However, this flickering network has an important advantage, a significant number of the radiobeacons are stationary, and this subset is known and is part of a stationary ad hoc network, for example all the radiobeacons in all the department stores, plus any radiobeacons placed by private or governmental users. In some cases, thousands of these low energy radiobeacons are powered up and affixed in defined locations. Thus inertial activity detected by an accelerometer sensor package in a radiobeacon indicates a relative movement, and when multiple radiobeacons report a synchronous movement of about the same magnitude over a local area, there is a high likelihood that an earthquake is occurring. Cellphones have been tested to detect earthquakes, but not successfully. The GPS system of a cellphone is sensitive enough to report a major ground shift, but cellphones are subjected to continuous jostling in normal use, so the motion signal is not readily pulled out of background motion and signal noise. Now, surprisingly, a radiobeacon matrix covering an urban area will report a clean signal of a coordinated earth motion. By capturing this data on an ad hoc switching network of nodal devices and aggregating it at a cloud server, the spread of a seismic event can be detected with such rapidity that persons outside the epicenter can be warned of an approaching seismic wave. The cloud host will analyze sensor data in real time and may be programmed to send out an alert estimating the size of the earthquake and an estimate of the areas in which it will be felt or cause damage, and then send a report to all users in those areas, as well as contacting authorities. Thus while a cellphone network fitted with accelerometers may be limited to detecting very strong events, Magnitude 7 or higher, when queries, a radiobeacon network and a population of nodal devices can spontaneously function as an earthquake sensor for Magnitude 4 earthquakes or lower, and can detect the initial P wave of an earthquake so as to maximize the response time in getting out a notification to all users in the area ahead of the seismic wave. Radiobeacons can also monitor radio traffic and can detect urban congestion, any kind of disturbance, and so forth, and because the soft switch operates in background, the data can be transmitted as a “micro-message” to the internetwork without interference by cellphones, which typically become overloaded during emergencies.

Example V

In yet another instance, the radiobeacon may be attached to something of value, such as a laptop computer. Then if the owner of the laptop or cellphone reports the item lost to the cloud server, the cloud host server will tag any report of a radio contact with the radiotag by any anonymous user anywhere. This occurs without a query from the cloud server and in background on a limited resource network, without direct participation of any users. Reports of radio contacts are sent as messages to the cloud host server using a soft switch of the invention. This example recognizes that radio contacts are routinely recognized by nodal devices, and turns this to advantage by switching over any message attached to a radio contact having a characteristic beacon signal to an internetwork compatible radioset for transmission to a dedicated cloud host an administrative database for tracking. The radio contact data that is transmitted to the cloud host will typically include a timestamp. In some instances, background resources of devices owned by anonymous users may also be able to provide a geostamp, or the devices may have a history of recently being in proximity to a radiobeacon having a fixed location. And by collating this information, the cloud host is able to provide a trail of radio contacts to the owner, thereby assisting the owner in localizing the current location of the lost item and recovering it. In this way spontaneous, anonymous and unsolicited sharing of resources provides a benefit with minimal cost to any user. In some instances location data is encoded by bit-overloading within the data structure of an ordinary beacon transmission.

Example VI

The disclosures of the invention enable a wide range of applications, many of which have not yet been conceived. However, the inventors are in possession of a system enabling a range of applications representative of future uses, the system having general applicability based on sharing of background resources for compact background messaging in a bottom-up architecture, where the cloud host does not generally query available resources but instead receives a promiscuous and spontaneous stream of flickering micro-messages that can be assembled into coherent contextual data on which decisions can be made, either as selected by particular owners for example of a particular radiobeacon originating a message, or at the system level, for example based on aggregated data collected from multiple community resources. Here are samples of other applications:

-   -   one-click ordering a pizza using a radiobeacon in which a button         press is encoded in a message that is transmitted through a         nodal device to a cloud host server;     -   one-click engagement of cruise control on a computer-enabled         vehicle while in gear;     -   one-click engagement of steering on an automatically steered         vehicle while taking a telephone call;     -   multi-click engagement of a “Nest” or “HomeKit” that controls         home thermostat, smoke alarms, carbon monoxide alarms,         earthquake alarms, and other domestic functions such as a garage         door, security camera, or locks;     -   automatic (no click) functions such as auto-locking of hard         drives when an earthquake P-wave is detected approaching a         compatible user device;     -   automatic (no click) functions such as notification of first         responders when a sound of a gunshot is detected, a smoke alarm         goes off, a door lock is forced without a key; or motion is         detected in an expectedly vacant house or office;     -   automatic (no click) alerts when a prolonged QT heart rhythm is         detected;     -   one-click uploading of a document from a remote computer to a         “Google Drive” account;     -   multi-click semi-automated formatting and sending of a message         to an email or SMS account of a recipient, either through an         Android function of a smart phone or indirectly when executed in         IOS on an iPhone (Android 4.0 and higher or iOS 7.0 and higher);     -   one-click categorization of emails into junk, spam, archive, or         priority accounts;     -   one-click access to a local map using smart device resources;     -   one-click silencing of a ring function on a smart phone, with         multi-click instruction for a making pre-programmed response by         a virtual answering machine or taking a message;     -   one-click activation or inactivation of voice command mode in         any compatible application; and/or,     -   multi-click selection and play from a playlist on any compatible         music device.

All these applications have the advantage of shortcutting many API's and interfaces that the user must otherwise individually engage to get to the desired functionality. Reducing the “system behavior” to a single click, a no-click, or a multi-click switch status enables the system to detect the switch status and immediately implement a pre-programmed response. For repetitive and emergency system behaviors, there is a corresponding reduction in labor and an increase in system responsiveness in both speed of response and accuracy. The precise nature of the response is dependent on sensor content of the message, which may be as simple as a HIGH or LOW position of a button, or may be a more complex function that integrates context, such as time of day, day of week, weather conditions, pulse rate, or vehicle performance indicia input from an ODB sensor panel, traffic hazard sensing and route plan input from a route mapping service, and various combinations of sensor inputs and big data. In addition, the system operator can update and add new functions on the host cloud server so that system upgrades are implemented by redirecting the messages from a community device to the cloud host server and back, using control loop architecture having a signal transmission and command response, eliminating or complementing the need for periodic new releases of software to the member devices.

INCORPORATION BY REFERENCE

All of the U.S. patents, U.S. Patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and related filings are incorporated herein by reference in their entirety for all purposes.

Scope of the Claims

The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the invention. Thus, the foregoing descriptions of specific embodiments of the present invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed. It will be apparent to one of ordinary skill in the art that many modifications and variations are possible in view of the above teachings.

The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.

In general, in the following claims, the terms used in the written description should not be construed to limit the claims to specific embodiments described herein for illustration, but should be construed to include all possible embodiments, both specific and generic, along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited in haec verba by the disclosure. 

We claim:
 1. A system for upswitching sensor and identification data contained in a low energy radio beacon message to a dedicated cloud host via at least one community nodal device in operative communication with a broad area network, the system comprising: (a) one or more radiobeacons having a sensor or sensor package, a radio emitter with antenna, an encoder, a device processor with supporting logic circuitry, and memory for storing data and an instruction set to be executed by said device processor, wherein said radiobeacon or radiobeacons are configured to emit a low energy radio message or messages that include an owner unique identifier, a community unique identifier, and a sensor payload; wherein said unique identifiers define a qualified radio signal; (b) a broad area network, said broad area network having a cloud host, said cloud host having a dedicated cloud IP address associated with said community of members, wherein said cloud host is configured to identify a qualified hub radio signal, an owner of record of the qualified hub radio signal, and any sensor payload in said qualified radio signal; (c) one or more smart devices of a plurality of smart devices, each said smart device having a registered owner; wherein said smart devices are configured to receive a command or notification from said cloud host; (d) an application installable on said one or more smart devices; wherein said application is enabled to: i) reconfigure said one or more smart devices as each a community nodal device, each said community nodal device having permission to use background resources thereof to separate said qualified radio signal from unidentifiable signals, to dump said unidentifiable signals, to time stamp said qualified radio signal, and to disable foreground disclosure thereof when said owner of record of said qualified radio signal is not said private owner of said radiobeacon or radiobeacons; ii) format said qualified radio signal as a radio message addressed to said dedicated cloud IP address associated with said community of members; and, iii) use background resources to forward broadcast said radio message on said broad area network to said cloud host; (e) further wherein said cloud host is enabled to receive said qualified radio signal from one or more of said community nodal devices; i) parse said qualified radio message to identify an owner of record and any sensor payload; ii) formulate said command or notification in response thereto according to rules established by said owner of record, said community of members, and said sensor payload; and, iii) transmit said command or notification over said broad area network to at least one smart device or community nodal device of said plurality of smart devices, to a remote machine, to an actuation device, or to a combination thereof.
 2. The system of claim 1, further wherein said qualified radio signal is processed at an administrative server of said cloud host, wherein said administrative server is configured with an administrative database and an instruction set with instructions to: a) parse said radio message so as to extract said owner unique identifier, said community unique identifier, said sensor payload, and any associated timestamp, proximity measurement, or geostamp coded therein; b) formulate said command or notification based on one or more of i) a rule or rules associated with said owner of record; ii) a rule or rules implemented by a system administrator on behalf of said owner or said community of members; and, iii) any contextual or aggregate data available to said server.
 3. The system of claim 2, wherein said application is configured to suspend any process enabled to process said message in foreground services if said owner of record of said qualified radio signal is said registered owner of said smart device and if said foreground services are unresponsive, and automatically upswitch and forward broadcast said message in background to said cloud host server for disposition according to rules associated with said private owner of said smart device, any rules implemented by a system administrator on behalf of a community of members, and any contextual or aggregate data available to said system.
 4. The system of claim 2, wherein said cloud host is configured to transmit said command to said plurality of smart devices, wherein said command is a command to display a notification to a community of members having converted their smart devices to community nodal devices.
 5. The system of claim 2, wherein said application is configured to assemble and configure a smart switch from hardware resources of said community device; to dump any record or content of said message from said community nodal device on completion of said forward broadcast to said cloud host server; and, thereby to reversibly use and release any hardware resources shared by said community device each time said soft switch is required for operation of said application.
 6. The system of claim 2, wherein said cloud host is configured to transmit a command over said broad area network to a remote machine, an actuation device, a hub, or a plurality thereof.
 7. The system of claim 6, comprising transmitting said command to said plurality of remote machines or actuation devices, wherein said command is a command to execute a machine action or to actuate a device.
 8. The system of claim 2, wherein said sensor or sensor package of said one or more beacons comprise a sensor or sensors selected from a photocell, a radiation sensor, a motion sensor, a velocity sensor, an accelerometer, a jolt sensor, a gyroscopic sensor, a gesture sensor, a gravitational sensor, a magnetic field sensor, a compass, a local time sensor, a switch open/switch closed sensor, a vibration sensor, an audio pattern detection sensor, a vehicle performance sensor, a biological agent sensor, a biochemical agent sensor, a chemical agent sensor, a temperature sensor, a pressure sensor, a humidity sensor, a windspeed sensor, a location sensor, a global positioning satellite sensor, a proximity sensor, a relative radio signal strength sensor, or a radio traffic sensor.
 9. The system of claim 2, wherein said system comprises a hub.
 10. The system of claim 8, wherein said command is directed to a smart device, a remote machine, or an actuation device according to a location datum received from a radiobeacon conditionally on whether said radiobeacon is stationary and known to said system, or mobile and deduced from an aggregation of radio messages.
 11. The system of claim 8, wherein said command is directed to a plurality of smart devices, remote machines, or actuation devices according to a location datum received from said sensor or sensor package, from said nodal device, from a radiobeacon conditionally on whether said radiobeacon is stationary and known to said system, or mobile and deduced from an aggregation of radio messages.
 12. The system of claim 2, wherein said command is configured to accord with rules established by an owner of said radiobeacon or an operator of said administrative server, said rules being conditional according to said sensor payload.
 13. The system of claim 2, wherein said command is configured to accord with rules established by an owner of said radiobeacon or an operator of said administrative server, said rules being conditioned upon said context as known to said administrative server.
 14. The system of claim 8, wherein said administrative server is configured to store a chronological record of said sensor payloads of an aggregation of messages.
 15. The system of claim 8, wherein said administrative server is configured to compile and share a map or plot display in which sensor data is graphically displayed in aggregate, or graphically displayed with trend lines, or graphically displayed with an updatable tracker function.
 16. The system of claim 2, wherein said administrative server is configured to provide a cloud-based service for graphically displaying the location of a lost object as tracked by a radiotag defined by said owner unique identifier and a community unique identifier in the form of a track or path superimposed on said map, wherein said map is updated when said administrative server receives a fresh radio contact and location of said lost object, said track comprising a chronological record of recent contacts in a mapped sequence.
 17. The system of claim 2, wherein said administrative server is configured to provide a cloud-based service for mapping the location of a friend.
 18. The system of claim 1, wherein said radio message includes a unique identifier value, a major value, a minor value, and a sensor payload for each of a plurality of radiobeacons in a local area, wherein said administrative database is configured to map said sensor payload according to a known location of each of said radiobeacons and to generate a display that displays aggregated most recent or aggregated historically trending sensor data from each of said radiobeacons, such that said display is continuously refreshed and can be accessed to support user queries.
 19. The system of claim 1, wherein said radiobeacon includes at least one button, and said radio message includes a sensor data payload, said sensor data payload includes a state of said button, and further wherein: a) said button is configured to generate a message when pressed that will be recognized at cloud host server as a call for help or vigilance; b) said community nodal devices are configured to convey said message from said radiobeacon to said cloud host server through said plurality of community nodal devices; and, c) said cloud host is configured to transmit a command and a notification to a first responder or to said community nodal devices, including a timestamp and a location of said radiobeacon.
 20. The system of claim 19, wherein said cloud host is configured to command an increase in illumination, strobe lamps, or sound of an alarm at the location of said radiobeacon, or to activate a camera at the location when said button is pressed and said message is received at said cloud host server. 